I really like the Multijob plugin (<https://wiki.jenkins-ci.org/display/JENKINS/Multijob+Plugin>), though I see there is some encouragement to move to the Pipelines conglomeration. For my purposes, Multijob is more straight-forward and presents clear results. It includes a potentially very helpful feature, the ability to skip a build if SCM has not changed since the last successful build. But that isn't working right for us so I'd appreciate some advice.
Most of our builds are not from the GIT master branch but from other branches. We pass a parameter to jobs to specify which branch to use. However, it appears that Multijob always checks for changes on the master branch. Since that branch doesn't change often, the effect is to skip builds which should occur. Does anyone know a way, without trying to modify the code, to get Multijob to check a different branch? -- Dave Close -- 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/3b2e06f6-3441-866f-956f-eef362a46fbb%40us.thalesgroup.com. For more options, visit https://groups.google.com/d/optout.
