[HADOOP-18125] Utility to identify git commit / Jira fixVersion discrepancies for RC preparation

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0, 2.10.2, 3.2.3, 3.3.3
• Fix Version/s: 3.4.0, 2.10.2, 3.2.3, 3.3.3
• Component/s: build
• Labels: pull-request-available
• Target Version/s: 3.4.0, 3.3.3
• Hadoop Flags: Reviewed
• Assignee: Viraj Jasani
• Reporter: Viraj Jasani
• Created: 14/Feb/22 09:42
• Updated: 12/Feb/24 07:41
• Resolved: 18/Apr/22 14:18

Description

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:

1. commit is reverted as per commit message
2. commit does not contain Jira number format (e.g. HADOOP-XXXX / HDFS-XXXX etc) in message
3. Jira does not have expected fixVersion
4. Jira has expected fixVersion, but it is not yet resolved
5. Jira has release corresponding fixVersion and is resolved, but no corresponding commit yet found

It can take inputs as:

1. First commit hash to start excluding commits from history
2. Fix Version
3. JIRA Project Name
4. Path of project's working dir
5. Jira server url

Issue Links

• is depended upon by: HADOOP-18198 Release Hadoop 3.3.3: hadoop-3.3.2 with some fixes
• links to: GitHub Pull Request #3991