[jira] [Commented] (KUDU-1566) JIRA updater script linking a gerrit patch to JIRA automatically

[Dinesh Bhat (JIRA)]

[ 
https://issues.apache.org/jira/browse/KUDU-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15621472#comment-15621472
 ] 

Dinesh Bhat commented on KUDU-1566:
---

commit c105fefde20798e9f3671419ca9638a0affea1e5
Author: Dinesh Bhat 
Date:   Tue Oct 25 23:49:29 2016 -0700

[scripts] KUDU-1566: Update jira fields automatically

This script is intended to be merged with our existing tools - like
pre-push or post-commit, for all commits which start with a JIRA id
in their COMMIT_MSG. This helps to track the review patches to JIRA
domain and vice versa thereby making it easy to navigate between the
two worlds. Currently it comments on the JIRA issue by parsing the
commit log for the presence of 'KUDU-[1-9]+' string, and it also
updates a review link against 'Code Review' field in jira.

Also, it can be leveraged to automatically resolve a JIRA if optional
'--resolve=True' is provided.

Change-Id: I4519ee0b83f9af03ba55f0eacc0553e86a3f13ec


> JIRA updater script linking a gerrit patch to JIRA automatically
> 
>
> Key: KUDU-1566
> URL: https://issues.apache.org/jira/browse/KUDU-1566
> Project: Kudu
>  Issue Type: Task
>Reporter: Dinesh Bhat
>Assignee: Dinesh Bhat
>Priority: Minor
> Fix For: 1.1.0
>
>
> At times, I have found it hard to track a particular JIRA to a gerrit patch 
> and vice versa to gain more context on a submitted change, code review 
> discussions, etc. I am hoping this will bridge the gap between the review 
> system and JIRA tracking.
> Currently, all of our commits do not carry JIRA numbers, but this could be 
> applicable to whichever gerrit patch carries one in its commit message. I 
> have come across such scripts before, so spinning one shouldn't be that hard. 
> Though not as fancy as the below link, we could just add a gerritt link to 
> JIRA comment section whenever a change is submitted(or perhaps posted for 
> review).
> https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/cloud/overview



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KUDU-1566) JIRA updater script linking a gerrit patch to JIRA automatically

[Dinesh Bhat (JIRA)]

[ 
https://issues.apache.org/jira/browse/KUDU-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15621453#comment-15621453
 ] 

Dinesh Bhat commented on KUDU-1566:
---

commit c105fefde20798e9f3671419ca9638a0affea1e5
Author: Dinesh Bhat 
Date:   Tue Oct 25 23:49:29 2016 -0700

[scripts] KUDU-1566: Update jira fields automatically

This script is intended to be merged with our existing tools - like
pre-push or post-commit, for all commits which start with a JIRA id
in their COMMIT_MSG. This helps to track the review patches to JIRA
domain and vice versa thereby making it easy to navigate between the
two worlds. Currently it comments on the JIRA issue by parsing the
commit log for the presence of 'KUDU-[1-9]+' string, and it also
updates a review link against 'Code Review' field in jira.

Also, it can be leveraged to automatically resolve a JIRA if optional
'--resolve=True' is provided.

Change-Id: I4519ee0b83f9af03ba55f0eacc0553e86a3f13ec


> JIRA updater script linking a gerrit patch to JIRA automatically
> 
>
> Key: KUDU-1566
> URL: https://issues.apache.org/jira/browse/KUDU-1566
> Project: Kudu
>  Issue Type: Task
>Reporter: Dinesh Bhat
>Assignee: Dinesh Bhat
>Priority: Minor
>
> At times, I have found it hard to track a particular JIRA to a gerrit patch 
> and vice versa to gain more context on a submitted change, code review 
> discussions, etc. I am hoping this will bridge the gap between the review 
> system and JIRA tracking.
> Currently, all of our commits do not carry JIRA numbers, but this could be 
> applicable to whichever gerrit patch carries one in its commit message. I 
> have come across such scripts before, so spinning one shouldn't be that hard. 
> Though not as fancy as the below link, we could just add a gerritt link to 
> JIRA comment section whenever a change is submitted(or perhaps posted for 
> review).
> https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/cloud/overview



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KUDU-1566) JIRA updater script linking a gerrit patch to JIRA automatically

[Dinesh Bhat (JIRA)]

[ 
https://issues.apache.org/jira/browse/KUDU-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15621451#comment-15621451
 ] 

Dinesh Bhat commented on KUDU-1566:
---

commit c105fefde20798e9f3671419ca9638a0affea1e5
Author: Dinesh Bhat 
Date:   Tue Oct 25 23:49:29 2016 -0700

[scripts] KUDU-1566: Update jira fields automatically

This script is intended to be merged with our existing tools - like
pre-push or post-commit, for all commits which start with a JIRA id
in their COMMIT_MSG. This helps to track the review patches to JIRA
domain and vice versa thereby making it easy to navigate between the
two worlds. Currently it comments on the JIRA issue by parsing the
commit log for the presence of 'KUDU-[1-9]+' string, and it also
updates a review link against 'Code Review' field in jira.

Also, it can be leveraged to automatically resolve a JIRA if optional
'--resolve=True' is provided.

Change-Id: I4519ee0b83f9af03ba55f0eacc0553e86a3f13ec


> JIRA updater script linking a gerrit patch to JIRA automatically
> 
>
> Key: KUDU-1566
> URL: https://issues.apache.org/jira/browse/KUDU-1566
> Project: Kudu
>  Issue Type: Task
>Reporter: Dinesh Bhat
>Assignee: Dinesh Bhat
>Priority: Minor
>
> At times, I have found it hard to track a particular JIRA to a gerrit patch 
> and vice versa to gain more context on a submitted change, code review 
> discussions, etc. I am hoping this will bridge the gap between the review 
> system and JIRA tracking.
> Currently, all of our commits do not carry JIRA numbers, but this could be 
> applicable to whichever gerrit patch carries one in its commit message. I 
> have come across such scripts before, so spinning one shouldn't be that hard. 
> Though not as fancy as the below link, we could just add a gerritt link to 
> JIRA comment section whenever a change is submitted(or perhaps posted for 
> review).
> https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/cloud/overview



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KUDU-1566) JIRA updater script linking a gerrit patch to JIRA automatically

[Dinesh Bhat (JIRA)]

[ 
https://issues.apache.org/jira/browse/KUDU-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15621447#comment-15621447
 ] 

Dinesh Bhat commented on KUDU-1566:
---

commit c105fefde20798e9f3671419ca9638a0affea1e5
Author: Dinesh Bhat 
Date:   Tue Oct 25 23:49:29 2016 -0700

[scripts] KUDU-1566: Update jira fields automatically

This script is intended to be merged with our existing tools - like
pre-push or post-commit, for all commits which start with a JIRA id
in their COMMIT_MSG. This helps to track the review patches to JIRA
domain and vice versa thereby making it easy to navigate between the
two worlds. Currently it comments on the JIRA issue by parsing the
commit log for the presence of 'KUDU-[1-9]+' string, and it also
updates a review link against 'Code Review' field in jira.

Also, it can be leveraged to automatically resolve a JIRA if optional
'--resolve=True' is provided.

Change-Id: I4519ee0b83f9af03ba55f0eacc0553e86a3f13ec


> JIRA updater script linking a gerrit patch to JIRA automatically
> 
>
> Key: KUDU-1566
> URL: https://issues.apache.org/jira/browse/KUDU-1566
> Project: Kudu
>  Issue Type: Task
>Reporter: Dinesh Bhat
>Assignee: Dinesh Bhat
>Priority: Minor
>
> At times, I have found it hard to track a particular JIRA to a gerrit patch 
> and vice versa to gain more context on a submitted change, code review 
> discussions, etc. I am hoping this will bridge the gap between the review 
> system and JIRA tracking.
> Currently, all of our commits do not carry JIRA numbers, but this could be 
> applicable to whichever gerrit patch carries one in its commit message. I 
> have come across such scripts before, so spinning one shouldn't be that hard. 
> Though not as fancy as the below link, we could just add a gerritt link to 
> JIRA comment section whenever a change is submitted(or perhaps posted for 
> review).
> https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/cloud/overview



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KUDU-1566) JIRA updater script linking a gerrit patch to JIRA automatically

[Dinesh Bhat (JIRA)]

[ 
https://issues.apache.org/jira/browse/KUDU-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15621446#comment-15621446
 ] 

Dinesh Bhat commented on KUDU-1566:
---

commit c105fefde20798e9f3671419ca9638a0affea1e5
Author: Dinesh Bhat 
Date:   Tue Oct 25 23:49:29 2016 -0700

[scripts] KUDU-1566: Update jira fields automatically

This script is intended to be merged with our existing tools - like
pre-push or post-commit, for all commits which start with a JIRA id
in their COMMIT_MSG. This helps to track the review patches to JIRA
domain and vice versa thereby making it easy to navigate between the
two worlds. Currently it comments on the JIRA issue by parsing the
commit log for the presence of 'KUDU-[1-9]+' string, and it also
updates a review link against 'Code Review' field in jira.

Also, it can be leveraged to automatically resolve a JIRA if optional
'--resolve=True' is provided.

Change-Id: I4519ee0b83f9af03ba55f0eacc0553e86a3f13ec


> JIRA updater script linking a gerrit patch to JIRA automatically
> 
>
> Key: KUDU-1566
> URL: https://issues.apache.org/jira/browse/KUDU-1566
> Project: Kudu
>  Issue Type: Task
>Reporter: Dinesh Bhat
>Assignee: Dinesh Bhat
>Priority: Minor
>
> At times, I have found it hard to track a particular JIRA to a gerrit patch 
> and vice versa to gain more context on a submitted change, code review 
> discussions, etc. I am hoping this will bridge the gap between the review 
> system and JIRA tracking.
> Currently, all of our commits do not carry JIRA numbers, but this could be 
> applicable to whichever gerrit patch carries one in its commit message. I 
> have come across such scripts before, so spinning one shouldn't be that hard. 
> Though not as fancy as the below link, we could just add a gerritt link to 
> JIRA comment section whenever a change is submitted(or perhaps posted for 
> review).
> https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/cloud/overview



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)