Quantcast

Getting started with Multibranch pipeline

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Getting started with Multibranch pipeline

David Aldrich-2

Hi

 

I am just getting started with the Multibranch pipeline project type (though I am familiar with conventional job types).

 

I am not using Docker.  The job will run on multiple svn branches and will simply run a command step to build our C++ software using a makefile.

 

I want to store my Jenkinsfile in svn.  Where on the configuration page do I specify the location of the Jenkinsfile? 

 

Best regards

 

David

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/bc4c7ce228e54067bad6ecabbab2f74b%40EUX13SRV1.EU.NEC.COM.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Getting started with Multibranch pipeline

Christopher Orr
Hi there,

On Wed, 19 Apr 2017, at 10:03, David Aldrich wrote:
> I am just getting started with the Multibranch pipeline project type
> (though I am familiar with conventional job types).
>
> I am not using Docker.  The job will run on multiple svn branches and
> will simply run a command step to build our C++ software using a
> makefile.
>
> I want to store my Jenkinsfile in svn.  Where on the configuration page
> do I specify the location of the Jenkinsfile?

You need to tell Jenkins where to find the branches that you want to
build — this is called the "branch source".  So long as you have the
Subversion plugin installed, you'll see it listed as a branch source;
see the screenshot in the documentation:
https://jenkins.io/doc/book/pipeline/multibranch/#creating-a-multibranch-pipeline

Jenkins will then inspect each of the branches in the repo, and create a
new Pipeline job for any branches which contain a `Jenkinsfile` in the
root of the branch directory.

Regards,
Chris

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1492613647.3524194.949396448.2B33BCA9%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Getting started with Multibranch pipeline

David Aldrich-2
Hi Chris

Thanks for your answer.

> Jenkins will then inspect each of the branches in the repo, and create a new
> Pipeline job for any branches which contain a `Jenkinsfile` in the root of the
> branch directory.

Does that mean that only one Jenkinsfile is allowed per branch?  In other words, we can only define one Jenkins job per project? (We have a mapping of one project to one repo).

BR

David

> -----Original Message-----
> From: [hidden email] [mailto:jenkinsci-
> [hidden email]] On Behalf Of Christopher Orr
> Sent: 19 April 2017 15:54
> To: [hidden email]
> Subject: Re: Getting started with Multibranch pipeline
>
> Hi there,
>
> On Wed, 19 Apr 2017, at 10:03, David Aldrich wrote:
> > I am just getting started with the Multibranch pipeline project type
> > (though I am familiar with conventional job types).
> >
> > I am not using Docker.  The job will run on multiple svn branches and
> > will simply run a command step to build our C++ software using a
> > makefile.
> >
> > I want to store my Jenkinsfile in svn.  Where on the configuration
> > page do I specify the location of the Jenkinsfile?
>
> You need to tell Jenkins where to find the branches that you want to build —
> this is called the "branch source".  So long as you have the Subversion plugin
> installed, you'll see it listed as a branch source; see the screenshot in the
> documentation:
> https://jenkins.io/doc/book/pipeline/multibranch/#creating-a-multibranch-
> pipeline
>
> Jenkins will then inspect each of the branches in the repo, and create a new
> Pipeline job for any branches which contain a `Jenkinsfile` in the root of the
> branch directory.
>
> Regards,
> Chris
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [hidden email].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-
> users/1492613647.3524194.949396448.2B33BCA9%40webmail.messagingengi
> ne.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
>  Click
> https://www.mailcontrol.com/sr/qFxsHo5nDhfGX2PQPOmvUiOFufhVdryLJ4Xc
> nm5y4z114yT4y7pCP3hZsQerBlcPyravz0G9yzomMzVbnZsAVw==  to report
> this email as spam.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c127408aefc540379bfa40e5575e07ff%40EUX13SRV1.EU.NEC.COM.
For more options, visit https://groups.google.com/d/optout.
Loading...