[
https://issues.apache.org/jira/browse/CASSANDRA-17753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17622148#comment-17622148
]
Stefan Miklosovic commented on CASSANDRA-17753:
-----------------------------------------------
I am +1 on this (1) branch as CASSANDRA-17974 is resolved. Build is running
here (2)
(1) includes my proposal to log Git SHA log on startup.
(1) https://github.com/apache/cassandra/pull/1941/commits
(2)
https://app.circleci.com/pipelines/github/instaclustr/cassandra/1478/workflows/bc7ff95f-1464-44f9-897b-8cc181d266b9
> 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: 2h 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
