One Jenkinsfile per repo in multi-branch workflows?

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

One Jenkinsfile per repo in multi-branch workflows?

David Aldrich-2

Hi

 

As the free-style Multi-Branch Project plugin is deprecated, I am experimenting with the Multibranch Pipeline job type.

 

With the Multi-Branch Project plugin it was possible to have multiple multi-branch jobs.  We took advantage of that and had multiple jobs to build different executables in the repo and to run different regression tests, with different polling periods.

 

It seems that the Multibranch Pipeline supports only one build script  per repo, defined by the JenkinsFile in the root directory.

 

This seems to me to be restrictive.  What is the thinking behind it and is it possible to define multiple multi-branch pipeline jobs per repo?

 

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/b96ace8205f74e2588f245cc43b83ac1%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

One Jenkinsfile per repo in multi-branch workflows?

Yotam Shapira
There seems to be some work done in this regard, but it seems to be lagging, so I can't tell if it's going to stay this way or not.
https://issues.jenkins-ci.org/plugins/servlet/mobile#issue/JENKINS-34561

--
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/fcfb912c-a998-440a-b85c-1bb06035a9c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: One Jenkinsfile per repo in multi-branch workflows?

David Aldrich-2
> There seems to be some work done in this regard, but it seems to be lagging,
> so I can't tell if it's going to stay this way or not.

Thanks for your answer. Good to know it is being worked on.

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/ceea20b58330439ea6efcfc1ad88a429%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: One Jenkinsfile per repo in multi-branch workflows?

Matt Stave
In reply to this post by David Aldrich-2
You can use a JobDSL statement in the Jenkinsfile in the root of your repo to generate other jobs.  Those jobs wouldn't be triggered by subsequent repo changes, unless you add a call to them in your main Jenkinsfile - they also could be triggered on-demand, through replay, a cron ...

--- Matt

On Thursday, May 18, 2017 at 9:38:28 AM UTC-5, David Aldrich wrote:

Hi

 

As the free-style Multi-Branch Project plugin is deprecated, I am experimenting with the Multibranch Pipeline job type.

 

With the Multi-Branch Project plugin it was possible to have multiple multi-branch jobs.  We took advantage of that and had multiple jobs to build different executables in the repo and to run different regression tests, with different polling periods.

 

It seems that the Multibranch Pipeline supports only one build script  per repo, defined by the JenkinsFile in the root directory.

 

This seems to me to be restrictive.  What is the thinking behind it and is it possible to define multiple multi-branch pipeline jobs per repo?

 

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/4b45b914-1cdf-4dfe-9076-330fea88798c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: One Jenkinsfile per repo in multi-branch workflows?

Michael Kobit

Be careful if you do use the job DSL as you will have to deal with Groovy sandbox permissions for job creation.


On Fri, May 19, 2017, 09:20 Matt Stave <[hidden email]> wrote:
You can use a JobDSL statement in the Jenkinsfile in the root of your repo to generate other jobs.  Those jobs wouldn't be triggered by subsequent repo changes, unless you add a call to them in your main Jenkinsfile - they also could be triggered on-demand, through replay, a cron ...

--- Matt


On Thursday, May 18, 2017 at 9:38:28 AM UTC-5, David Aldrich wrote:

Hi

 

As the free-style Multi-Branch Project plugin is deprecated, I am experimenting with the Multibranch Pipeline job type.

 

With the Multi-Branch Project plugin it was possible to have multiple multi-branch jobs.  We took advantage of that and had multiple jobs to build different executables in the repo and to run different regression tests, with different polling periods.

 

It seems that the Multibranch Pipeline supports only one build script  per repo, defined by the JenkinsFile in the root directory.

 

This seems to me to be restrictive.  What is the thinking behind it and is it possible to define multiple multi-branch pipeline jobs per repo?

 

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/4b45b914-1cdf-4dfe-9076-330fea88798c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/CALELY9F%3DWixhtxvoW0rFORs_Xtgp8N79dn3FWi8CMU4xgyB5Gw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Loading...