RE: Modifying Git branch dynamically

2013-06-27 Thread Kevin Fleming (BLOOMBERG/ 731 LEXIN)
y, June 27, 2013 12:54 PM To: jenkinsci-users@googlegroups.com Subject: Re: Modifying Git branch dynamically ok, I guess you have two use cases here that require distinct jobs. One of them may be an empty one, set for git hook to monitor develop branch, and just trigger the second one using par

RE: Modifying Git branch dynamically

2013-06-27 Thread Bob Bick
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Kevin Fleming (BLOOMBERG/ 731 LEXIN) Sent: Thursday, June 27, 2013 1:19 PM To: jenkinsci-users@googlegroups.com Subject: RE: Modifying Git branch dynamically You are; for Jenkins to do what it does (in this case, report on the code changes involved in

RE: Modifying Git branch dynamically

2013-06-27 Thread Kevin Fleming (BLOOMBERG/ 731 LEXIN)
, 2013 12:54 PM To: jenkinsci-users@googlegroups.com Subject: Re: Modifying Git branch dynamically ok, I guess you have two use cases here that require distinct jobs. One of them may be an empty one, set for git hook to monitor develop branch, and just trigger the second one using parameterized

RE: Modifying Git branch dynamically

2013-06-27 Thread Bob Bick
m] On Behalf Of nicolas de loof Sent: Thursday, June 27, 2013 12:54 PM To: jenkinsci-users@googlegroups.com Subject: Re: Modifying Git branch dynamically ok, I guess you have two use cases here that require distinct jobs. One of them may be an empty one, set for git hook to monitor develop branch, an

Re: Modifying Git branch dynamically

2013-06-27 Thread nicolas de loof
rry that was > not clear. > > ** ** > > *From:* jenkinsci-users@googlegroups.com [mailto: > jenkinsci-users@googlegroups.com] *On Behalf Of *nicolas de loof > *Sent:* Thursday, June 27, 2013 12:30 PM > > *To:* jenkinsci-users@googlegroups.com > *Subject:* Re:

RE: Modifying Git branch dynamically

2013-06-27 Thread Bob Bick
com<mailto:jenkinsci-users@googlegroups.com> Subject: Re: Modifying Git branch dynamically sole option I can see is to set branch specifier to $OVERRIDE_BRANCH with default value to "develop" So can't give advise without the long story ;) 2013/6/27 Bob Bick mailto:bb...@netj

Re: Modifying Git branch dynamically

2013-06-27 Thread nicolas de loof
t the > branch specifier to or CI branch (“develop”). > > ** ** > > *From:* jenkinsci-users@googlegroups.com [mailto: > jenkinsci-users@googlegroups.com] *On Behalf Of *nicolas de loof > *Sent:* Thursday, June 27, 2013 11:58 AM > *To:* jenkinsci-users@googlegroups.com > *Subject:* Re: Modif

RE: Modifying Git branch dynamically

2013-06-27 Thread Bob Bick
ers@googlegroups.com Subject: Re: Modifying Git branch dynamically sole option I can see is to set branch specifier to $OVERRIDE_BRANCH with default value to "develop" So can't give advise without the long story ;) 2013/6/27 Bob Bick mailto:bb...@netjets.com>> Hi, Backgrou

Re: Modifying Git branch dynamically

2013-06-27 Thread nicolas de loof
sole option I can see is to set branch specifier to $OVERRIDE_BRANCH with default value to "develop" So can't give advise without the long story ;) 2013/6/27 Bob Bick > Hi, > > ** ** > > *Background* > > ** ** > > Our Jenkins build job uses Git with a default branch specifier set to > ‘de