[
https://issues.apache.org/jira/browse/HBASE-22853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266523#comment-17266523
]
Viraj Jasani commented on HBASE-22853:
--------------------------------------
{code:java}
@property
def release_branch_refs(self):
""":obj:`list` of :obj:`git.refs.reference.Reference`: The git branches
identified as
"release branches", i.e., "branch-2.2"."""
refs = self.repo.remote(self._remote_name).refs
release_line_refs = self.release_line_refs
return [ref for ref in refs
if any([ref.name.startswith(release_line.name + '.')
for release_line in release_line_refs])]
{code}
Based on the code, it seems it already looks up in remote origin/branch-xx to
retrieve all release branches, however when I tried
*report-new-for-release-branch=origin/branch-2.4*, it failed with the error
that *origin/branch-2.4* is not found.
{code:java}
$ ./venv/bin/python3 ./git_jira_release_audit.py \
> --populate-from-git=false \
> --populate-from-jira=false \
> --branch-1-fix-version=1.7.0 \
> --branch-2-fix-version=2.5.0 \
> --report-new-for-release-branch=origin/branch-2.4
ERROR:git_jira_release_audit.py:release branch origin/branch-2.4 not found.
available options are ['origin/branch-1.0', 'origin/branch-1.1',
'origin/branch-1.2', 'origin/branch-1.3', 'origin/branch-1.4',
'origin/branch-2.0', 'origin/branch-2.1', 'origin/branch-2.2',
'origin/branch-2.3'].
{code}
> Git/Jira Release Audit Tool
> ---------------------------
>
> Key: HBASE-22853
> URL: https://issues.apache.org/jira/browse/HBASE-22853
> Project: HBase
> Issue Type: Task
> Components: build
> Reporter: Michael Stack
> Assignee: Nick Dimiduk
> Priority: Minor
> Fix For: 3.0.0-alpha-1
>
>
> Before cutting RC, need to make reconciliation between what's in JIRA and
> then what has been actually committed to ensure JIRA is accurate before
> starting the RC build (in order to ensure CHANGES/RELEASENOTES are accurate,
> etc.).
> Would be good to have a tool that compared git log for the release to
> fixVersion in JIRA (and then fixVersion in JIRA to what is in git) to ensure
> matching mentions in both places. It can get complicated when there has been
> reverts in git or when an issue is an umbrella issue w/ no direct patch
> associated in JIRA but tool could start out simple dumping out a list of
> hashes/JIRAs for the RM to 'check' where anomalies; i.e. mention in one
> system but not in the other. This would save on a bunch of work aligning the
> two systems. Could also do stuff like check git log to ensure all commits
> have associated JIRA, and so on.
> (Should there be a PR component?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
