Closed gnarf closed 11 years ago
@gnarf37 just post here when you can verify this is working as expected.
I just used it to build a build from jQuery so, seems to work correctly!
So, this now assumes origin
is "upstream". In a perfect world, that'd be configurable also.
Well origin will be whatever url you put in jenkins, presumably the URL that people are issuing pulls to right? :)
jquery/jquery#1041 btw - http://swarm.jquery.org:8080/job/Mergeatron%20jQuery/22/console
@steves, in these changes, @gnarf37 is assuming "upstream" is now origin, and "mergeatron" is origin. This brings a bit of clarity in the case where you clone "upstream" directly, which seems to make a little more sense. However, this can be tweaked to use upstream and origin if you'd prefer that.
Merge at will.
The assumption being when you setup the job in jenkins the "base" git URL will become the "origin" remote. The one that mergeatron manipulates becomes "mergeatron" - makes more sense to me, also seems shorter/more direct.
Oh - and also, it doesn't pollute local branches either, it does all its merge work in a headless state.
Just a suggestion for dealing with the merge part of jenkins bash script better.