[jira] [Commented] (HADOOP-12129) rework test-patch bug system support

["Allen Wittenauer (JIRA)" <ji...@apache.org>]

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

Allen Wittenauer commented on HADOOP-12129:
-------------------------------------------

There are a bunch of interleaved issues in play here.  This is a summary of some of the discussions that [~sekikn] and I had around these topics.

* Some projects use github PRs as their patch repository, with comments going to both github and JIRA.  In these projects (e.g., tajo), JIRA status is never patch available and a comment is made by an ASF infra bot in the JIRA that points to the github PR.  

* It's not uncommon to have JIRA point to another system for code reviews and patch repository via JIRA APIs.

* In the future, we should be able to support more than one bug system simultaneously.  e.g., github:project/#  jira:project/#  bugzilla:project/#  would push a precommit message to all three.

* In the far future, it'd be nice to be able to support multiples of the same comment system.

* Bonus points: How does reviewboard, gerrit, etc fit into this?

At a minimum, I think we need to do this list sooner rather than later:

a) pull more of the JIRA-specific code out of locate_patch and into the jira.sh plugin
b) support the not-patch-available-but-referenced-in-JIRA-comment use case

> rework test-patch bug system support
> ------------------------------------
>
>                 Key: HADOOP-12129
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12129
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: yetus
>            Reporter: Allen Wittenauer
>
> WARNING: this is a fairly big project.
> See first comment for a brain dump on the issues.



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