infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Nalley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-6757) The "perfect" Jira/Jenkins/ReviewBoard/Git integration
Date Wed, 04 Dec 2013 16:19:37 GMT

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

David Nalley commented on INFRA-6757:
-------------------------------------

So this sounds very similar to the Gerrit workflow (not that I am proposing that tool - completely
differently set of problems) 

CloudStack has something similar currently. 

Contributor creates a patch and submits via RB 
Jenkins tries to build it which run at least unit tests by default (see https://reviews.apache.org/r/13459/
for an example) and reports the outcome. 
A committer still needs to review and make a decision to commit or not. 
When the commit hits RB (and Jira if the issue number is included in the description) is updated
with the commit log message (see https://reviews.apache.org/r/15999/ and https://issues.apache.org/jira/browse/CLOUDSTACK-5364

That's largely built on the gitpubsub work from Daniel Gruno.  
 

> 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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message