|
||||||||
|
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.
Thanks for the clarification.
I believe the Git plugin intentionally polls all branches because it has a use case where users push branches to a central repository as "proposed changes", then Jenkins merges the content of those branches to an integration branch and pushes the resulting merge to the central repository. It has been referred to as "pre-tested commit" or "pre-tested merge".
I like that use case very much, since it allows me to submit a change to the central repository for Jenkins evaluation, and only if Jenkins evaluates it successfully will the change be merged to the destination branch.