|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I take it the reporter means he opens a pull request lets say from a fork with feature branch named feature01 to original repo's master branch. He wants the pull request builder plugin to test the pull request by testing against the PR merged into its destination (in this case merging PR which is created from feature01 to original repo's master branch) and attach the status of that merged pull request build. The comment should also indicated what was merged for the testing. This would be similar to the way Travis CI does this: http://travis-pr.herokuapp.com/image/slides/travisbot.png .
With the addition for this, we would actually test the merged version, rather than just the fork or feature branch. Thus, we also take into account changes made upstream after the repository has been forked.
FWIW this should only be possible if the Automerge button is available on the pull request. Perhaps we could have a global option in the plugin to allow for this, and you can override it in any specific job if you should so choose?