On Wed, Mar 7, 2012 at 12:25 AM, Didier Durand wrote:
> hi,
>
> i would use the label in config to hold branch name asnd then do a
> checkout including the label in the scm url via my own checkout in 1st
> build step if the if the variable can't be set directly in jenkins.
>
We build a lot of dif
hi,
i would use the label in config to hold branch name asnd then do a
checkout including the label in the scm url via my own checkout in 1st
build step if the if the variable can't be set directly in jenkins.
regards
didier
On Mar 7, 6:38 am, Les Mikesell wrote:
> On Tue, Mar 6, 2012 at 11:18
On Tue, Mar 6, 2012 at 11:18 PM, Didier Durand wrote:
>
> You can insert env variables in your paths on Jenkins SCM section in
> job configuration
>
> So, what you can do to avoid recreating jobs for branches is to put a
> variable for the path of the branch and set the value of the variable
> jus
Hi,
You can insert env variables in your paths on Jenkins SCM section in
job configuration
So, what you can do to avoid recreating jobs for branches is to put a
variable for the path of the branch and set the value of the variable
just before lanching build step ot the job. [I use this technique
Hi all
As we achieve more advanced build pipeline features with out Jenkins
jobs, we would now like to maintain those jobs in our SCM. Each time
we cut a new branch to continue developer we now find ourselves
recreating our Jenkins jobs to point to the new branch. I was just
wondering if anyone is
