[
https://issues.apache.org/jira/browse/CASSANDRA-17753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581089#comment-17581089
]
Abe Ratnofsky commented on CASSANDRA-17753:
-------------------------------------------
Thanks for the clarification [~mck] – this makes sense to me. I just pushed a
fix that checks if git is available first, and sets GitSHA=Unknown if not. I've
tested this in situations where git is available (git clone'd repo) and not
available (in the unzipped -src artifact directory) and it works as expected.
Mind taking another look?
> Include GitSHA in nodetool version output
> -----------------------------------------
>
> Key: CASSANDRA-17753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17753
> Project: Cassandra
> Issue Type: New Feature
> Components: Tool/nodetool
> Reporter: Abe Ratnofsky
> Assignee: Abe Ratnofsky
> Priority: Normal
> Fix For: 4.x
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> It can be useful to see specifically which Git SHA a running instance of
> Cassandra was built with, especially when running clusters in development for
> soak testing.
>
> I have a patch ready for this, and am preparing it now.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
