--
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 jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a86e14e1-f39c-4616-92b0-957cdc3374c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You could use the Pipeline Multibranch Defaults plugin which does the hardcoded in the job approachIf a stub file in Repo-A is acceptable you could also use a shared library to store the actual jenkinsfile as a script and the stub just containsdoRepoBuild() or similar which is the way jenkins plugin builds share build scripting. The blog post https://jenkins.io/blog/2017/10/02/pipeline-templates-with-shared-libraries/ runs through a more elaborate example with a bunch of parameters to a similar end.There are a few users which have done the parallel repo approach but I'm not myself sure of the details.Regards,Daniel
On Thu, Jul 4, 2019 at 1:51 PM Tom Brus <tom...@gmail.com> wrote:
Hi,--I have a repos I want to build all branches for (repos-A).I do not want to put any jenkinsfiles (or any other build related stuff) into this repos.My jenkinsfile lives in a separate repos (repos-B).So I need the branches from repos-A and I need the jenkinsfile to build with from repos-B.How can I set this up?- the Pipeline Multibranch Plugin only seems to allow "by Jenkinsfile" for mode- the Multi-Branch Project Plugin is deprecated so I like to stay away from it- I could live with a hardcaded jenkinsfile in the job itselfAny help welcome!Tom Brus
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 jenkins...@googlegroups.com.