[
https://issues.jenkins-ci.org/browse/JENKINS-13590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162610#comment-162610
]
Max Horn commented on JENKINS-13590:
------------------------------------
I would also love to have this. Indeed, going beyond it, whenever a pull
request is modified (a new commit added, rebased, etc.), another re-run should
be triggered, and ideally, the result of the test run would be posted as a
comment on the pull request.
Kind of like travis-ci.org does it, see
<http://about.travis-ci.org/blog/announcing-pull-request-support/>.
They do a bit more, though: Instead of building the remote branch from the pull
request, they instead do this:
1) merge the remote branch into master, report error if that fails
2) try to build the result of that merge (and perhaps also run test suite),
report error if that fails
Extra bonus if this becomes possible (I guess I could handle this with a custom
build, as long as it receives sufficient details about the pull request, such
as the branch name / commit hash, and the requester's username)
> Trigger build when new pull request occurs in github
> ----------------------------------------------------
>
> Key: JENKINS-13590
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13590
> Project: Jenkins
> Issue Type: New Feature
> Components: git, github
> Reporter: Miroslav Novak
> Assignee: Nicolas De Loof
> Priority: Critical
> Labels: git, jenkins, plugins
>
> We have a project in github and we would like to start new build whenever new
> pull request occurs. This run should test whether changes in pull request
> won't break the build. Right now we've a separate script which periodically
> scans open pull requests and checks lasts builds which of them were already
> run.
> This approach is used for JBoss AS7 or HornetQ project and appears to be best
> practice how to use git(hub).
> Thanks,
> Mirek
> P.S.
> I hope I don't duplicate another jira. I could not find it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
