We are about to switch our CI builds to jenkins and I would like to make
use of the multibranch builds but we have multiple projects in a single
repo which (as far as I can tell) won't work with the multibranch stuff as
we would need a Jenkinsfile per project, not one for the whole repo.
Our repo looks something like:
/
/libraryProject
build.xml
/projectA
build.xml
/projectB
build.gradle
where libraryProject builds a library jar that is published externally (to
a nexus repo). The projectA/B builds retrieve the artifact from that repo
when they build - so in that sense they are independent builds.
Ideally, what I'd like is to be able to do is have a Jenkinsfile in each of
the 3 projects, and have a multibranch build for each of them. This would
mean explicitly specifying the location of the Jenkinsfile per build
(similar to how the current pipeline build works). The other thing that
would be required is to only trigger the relevant build when repo changes
(ie: if code under the projectA directory changed - only trigger the
projectA multibranch build).
I don't think the above is possible at the moment (please let me know if
I'm wrong), but can anyone suggest a way to achieve the same result
(multiple multibranch pipeline builds from a single repo) with existing
plugins? Or is what I'm trying to do not possible at the moment?
Thanks
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/aa8c0318-d0bb-413e-8765-25410a6ee509%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
