-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HADOOP-18125. Utility to identify git commit / Jira fixVersion discrepancies for RC preparation #3991
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
…pancies for RC preparation
3edf1d3 to
ddaf8e0
Compare
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
jojochuang
approved these changes
Feb 16, 2022
Contributor
Author
|
Thanks for the review @jojochuang |
asfgit
pushed a commit
that referenced
this pull request
Feb 22, 2022
…pancies for RC preparation (#3991) Signed-off-by: Wei-Chiu Chuang <[email protected]> (cherry picked from commit 697e5d4) (cherry picked from commit d763c99)
asfgit
pushed a commit
that referenced
this pull request
Feb 22, 2022
…pancies for RC preparation (#3991) Signed-off-by: Wei-Chiu Chuang <[email protected]> (cherry picked from commit 697e5d4) (cherry picked from commit d763c99) (cherry picked from commit 9d618bc)
asfgit
pushed a commit
that referenced
this pull request
Feb 22, 2022
…pancies for RC preparation (#3991) Signed-off-by: Wei-Chiu Chuang <[email protected]> (cherry picked from commit 697e5d4)
iwasakims
pushed a commit
that referenced
this pull request
Mar 13, 2022
…pancies for RC preparation (#3991) Signed-off-by: Wei-Chiu Chuang <[email protected]> (cherry picked from commit 697e5d4) (cherry picked from commit d763c99) (cherry picked from commit 9d618bc)
steveloughran
pushed a commit
to steveloughran/hadoop
that referenced
this pull request
Apr 5, 2022
…pancies for RC preparation (apache#3991) Signed-off-by: Wei-Chiu Chuang <[email protected]> (cherry picked from commit 697e5d4)
steveloughran
pushed a commit
to steveloughran/hadoop
that referenced
this pull request
Apr 12, 2022
…pancies for RC preparation (apache#3991) Signed-off-by: Wei-Chiu Chuang <[email protected]> (cherry picked from commit 697e5d4)
asfgit
pushed a commit
that referenced
this pull request
Apr 13, 2022
…pancies for RC preparation (#3991) Signed-off-by: Wei-Chiu Chuang <[email protected]> (cherry picked from commit 697e5d4)
asfgit
pushed a commit
that referenced
this pull request
Apr 14, 2022
…pancies for RC preparation (#3991) Signed-off-by: Wei-Chiu Chuang <[email protected]> (cherry picked from commit 697e5d4)
HarshitGupta11
pushed a commit
to HarshitGupta11/hadoop
that referenced
this pull request
Nov 28, 2022
…pancies for RC preparation (apache#3991) Signed-off-by: Wei-Chiu Chuang <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of PR
As part of RC preparation, we need to identify all git commits that landed on release branch, however their corresponding Jira is either not resolved yet or does not contain expected fixVersions. Only when we have git commits and corresponding Jiras with expected fixVersion resolved, we get all such Jiras included in auto-generated CHANGES.md as per Yetus changelog generator.
Proposal of this Jira is to provide such script that can be useful for all upcoming RC preparations and list down all Jiras where we need manual intervention. This utility script should use Jira API to retrieve individual fields and use git log to loop through commit history.
The script should identify these issues:
It can take inputs as:
How was this patch tested?
Locally.
For code changes: