HBASE-22853 Git/Jira Release Audit Tool #1088
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is an application for performing an audit between the histories on our git branches and the `fixVersion` field set on issues in JIRA. It does this by building a Sqlite database from the commits found on each git branch, identifying Jira IDs and release tags, and then requesting information about those issues from Jira. Once both sources have been collected, queries can be performed against the database to look for discrepancies between the sources of truth (and, possibly, bugs in this script).
Member
Author
|
Heads up release managers/Jira janitors -- @infraio @Apache9 @busbey @apurtell @saintstack @joshelser |
|
💔 -1 overall
This message was automatically generated. |
Contributor
|
long term, this would make a nice contribution to Apache Yetus. |
busbey
reviewed
Jan 24, 2020
Contributor
busbey
left a comment
busbey
left a comment
There was a problem hiding this comment.
one doc gap. looks great, let's give it a go.
Member
Author
|
Huh so the usage of pylint is broken in our personality? |
Member
Author
I generally agree, but I wonder how much of this branching style is hbase-specific. |
joshelser
approved these changes
Jan 27, 2020
Member
joshelser
left a comment
joshelser
left a comment
There was a problem hiding this comment.
Minor docs questions, but this looks great!
virajjasani
approved these changes
Jan 27, 2020
Contributor
virajjasani
left a comment
virajjasani
left a comment
There was a problem hiding this comment.
This is cool, +1 overall :)
Contributor
yeah, I'm totally on board with us using it locally here first and then seeing if it's suitable for others later.
shoot, is it? I wonder how long ago that happened. can someone get up a jira with a description and I'll try to find someone to chase it down? |
Member
Author
|
Address PR feedback, burn down the pylint complaints. |
Member
Author
|
|
💔 -1 overall
This message was automatically generated. |
thangTang
pushed a commit
to thangTang/hbase
that referenced
this pull request
Apr 16, 2020
* HBASE-22853 Git/Jira Release Audit Tool This is an application for performing an audit between the histories on our git branches and the `fixVersion` field set on issues in JIRA. It does this by building a Sqlite database from the commits found on each git branch, identifying Jira IDs and release tags, and then requesting information about those issues from Jira. Once both sources have been collected, queries can be performed against the database to look for discrepancies between the sources of truth (and, possibly, bugs in this script). Signed-off-by: Sean Busbey <[email protected]> Signed-off-by: Josh Elser <[email protected]> Signed-off-by: Viraj Jasani <[email protected]>
thangTang
pushed a commit
to thangTang/hbase
that referenced
this pull request
Apr 16, 2020
* HBASE-22853 Git/Jira Release Audit Tool This is an application for performing an audit between the histories on our git branches and the `fixVersion` field set on issues in JIRA. It does this by building a Sqlite database from the commits found on each git branch, identifying Jira IDs and release tags, and then requesting information about those issues from Jira. Once both sources have been collected, queries can be performed against the database to look for discrepancies between the sources of truth (and, possibly, bugs in this script). Signed-off-by: Sean Busbey <[email protected]> Signed-off-by: Josh Elser <[email protected]> Signed-off-by: Viraj Jasani <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an application for performing an audit between the histories on our git branches and the
fixVersionfield set on issues in JIRA. It does this by building a Sqlite database from the commits found on each git branch, identifying Jira IDs and release tags, and then requesting information about those issues from Jira. Once both sources have been collected, queries can be performed against the database to look for discrepancies between the sources of truth (and, possibly, bugs in this script).