|
||||||||
|
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/d/optout.
The reason I created this is because if we create a new build and forget to add the 'additional behavior' of 'force new clone' any new builds fail because the branches on our build boxes aren't updated. After looking into it, I checked the console output and only see a 'git fetch' being performed, so the local branches aren't being updated. I don't see the plugin following it up with a git merge.
So I figured if the plugin can run a git pull by default then it would solve the issue of us having to add an additional behavior to every build we configure, to force a new clone (whihc btw also slows down master performance having to reclone a 8GB repository for every build, for example). Alternatively, if the plugin should be running a git merge after git fetch, that should work as well. Can you please confirm the plugin runs a git merge after fetch? Also, you mention the plugin allows user selection of merge strategy, where can this be setup in the UI? Is there a different place I need to assign this ticket?