[jira] [Closed] (INFRA-6757) The "perfect" Jira/Jenkins/ReviewBoard/Git integration

["Jake Farrell (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/INFRA-6757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jake Farrell closed INFRA-6757.
-------------------------------

    Resolution: Fixed
      Assignee: Jake Farrell

Jenkins (via scm automated builds with ticket id in commit message) and Reviewboard (add ticket id to the bugs field) will post a comment on the given ticket when the build finishes or issue is reviewed, the automating commits from each location this is the issue. If you have questions about setting either of these up for a project please let me know
                
> The "perfect" Jira/Jenkins/ReviewBoard/Git integration
> ------------------------------------------------------
>
>                 Key: INFRA-6757
>                 URL: https://issues.apache.org/jira/browse/INFRA-6757
>             Project: Infrastructure
>          Issue Type: New Feature
>          Components: Git, Jenkins, JIRA, Subversion
>            Reporter: Kevin Minder
>            Assignee: Jake Farrell
>
> I know this is probably a bit "pie in the sky" but I thought I'd put it out there anyway.  The steps below describe what I think is a pretty close to perfect development process.  The primary goal is to prevent commits/pushes that break the build while making committers lives a little bit easier.  Let me know if this is all just a beautiful dream or if this is actually something that could be accomplished.
> 1) A contributor attaches a patch to a Jira
> 2) A contributor presses the "Submit Patch" button
> 3) A Jenkins job is kicked off that runs a specific test suite with the patch merged locally
> 4) The results are added as a comment to the Jira
> 5) If the tests pass the patch is uploaded to ReviewBoard and a link is added to a Jira comment
> 6) A committer reviews the patch and the merge/test results and presses an "Apply Patch" button
> 7) A Jenkins job is kicked off that runs a specific test suite with the patch merged locally
> 8) If the merge has no conflicts and the tests pass then the patch is committed/pushed to the repo
> 9) The results are added as a comment to the Jira
> Note: Only committer's should have access to the "Apply Patch" button

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira