[ 
https://issues.apache.org/jira/browse/HBASE-22853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268031#comment-17268031
 ] 

Nick Dimiduk commented on HBASE-22853:
--------------------------------------

Hmm. What do you call the remote that corresponds to the upstream repository? 
If its anything other than {{origin}}, you'll need to tweak the git refs 
accordingly. Also make sure it's up to date, something like {{git remote update 
origin}}. You should see the branch show up in a listing like this,

{noformat}
$ git branch -a --list origin/branch-2.*
  remotes/origin/branch-2.0
  remotes/origin/branch-2.1
  remotes/origin/branch-2.2
  remotes/origin/branch-2.3
  remotes/origin/branch-2.4
{noformat}

Ping me on Slack and we can debug in real time.

> 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)

Reply via email to