How to Use Different Dependencies in Each Branch?

[John Mellor]

I'm building a large number of C++ projects on a Ubuntu host using the Jenkins free-style multi-branch project type, to run a shell script to run a pbuilder chroot jail that then runs the autotools, configure, make and then build one or more .deb files in each project.  Products delivered as .rpm or .exe or .tgz files would probably do this in essentially the same manner.  This works very well for every branch, with one exception.

If I want to build each branch with different dependencies, I'm stuck.  There does not seem to be a means in Jenkins to configure each branch separately.  Instead, for a small number of branches, I'm configuring a dedicated free-style single-branch project for each branch and building out the Jenkins dashboard display with a view to only show the builds that I care about for specific product releases.  This is very clunky, and does not work in the general case where I will be needing thousands of views to compensate for a lack of a configure mechanism per-branch.

I would expect this question to be a common problem that has been solved at a lot of sites already.  How do I configure a multi-branch build to have a different config per branch?

[Daniel Beck]

YAML Project Plugin or Literate Plugin might help. Basically, a job type that gets most of the "how to build" instructions from SCM.

> --
> 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/e9567450-f1f7-45cd-afe5-104f4b444913%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[John Mellor]

Thanks! However, neither one of those seem to be listed in the plugin manager as available plugins. Where do you get them?

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CF60EA4F-5C8E-4F2C-A0FD-451EE3F45AE3%40beckweb.net.

[Daniel Beck]

Both may only be available on the experimental update center as beta versions. There's an option in global Jenkins configuration to enable the experimental UC.

Otherwise, just download from http://updates.jenkins-ci.org/experimental/latest/

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/27e36b4f7b6c4ddab4e2d41a6427c9ed%40mbx01colo01p.esentire.local.