Odd - on my instance it's on the configuration page of the top level
"folder" instance. (Sorry can't be more precise as it's Saturday so not in
front of machine :) )
Richard
On Sat, 14 May 2016 1:10 am Mike Caspar wrote:
> Looked for that option.
>
> Repos are automatically scanned for Jenkiins
Awesome.
Thanks !
Mike
On 16-05-13 09:21 AM, Nigel Magnay wrote:
What we do is look at what the branch name is in the Jenkinsfile itself.
I.E:
if( branchName.equals("master") )
{
// deployment steps
}
On Fri, May 13, 2016 at 12:24 AM, Mike Caspar
mailto:mikecanbefo...@gmail.com>> wrote:
What we do is look at what the branch name is in the Jenkinsfile itself.
I.E:
if( branchName.equals("master") )
{
// deployment steps
}
On Fri, May 13, 2016 at 12:24 AM, Mike Caspar
wrote:
>
> I am working on a pipeline that does Test/Deploy after a commit.
>
> That's all cool!
>
> However.
Looked for that option.
Repos are automatically scanned for Jenkiinsfile, then added (with their
branches) to my Jenkins instance.
I can't find that option anywhere?
Could you point me to where I might find it ? Sound like it might work.
Mike
On 16-05-12 09:57 PM, Richard Bywater wrote:
Haven't done it myself but there is the different Property Strategy in the
multibranch config of "Named branches get different properties" - so
presumably you could set (or unset) a property for certain branches and
drive the decision to deploy off of that?
Richard.
On Fri, 13 May 2016 at 11:24 M
I am working on a pipeline that does Test/Deploy after a commit.
That's all cool!
HoweverWhen I create a branch (for a new feature), and it gets
auto-launched as a new build pipeline, how do I prevent the same
Jenkinsfile from initiating the Deploy step, since it's the same
Jeniinsfile ?
