Jenkins CI should support different jenkins projects depending on event
Problem to solve
We are using the Jenkins CI service to trigger builds on Jenkins for commits on feature branches and to build master after merging the feature branches. This works, but I would like to use two different jobs for the build in a feature branch and a build on the master.
Intended users
Jenkins CI Admins
Further details
The reasons to keep them distinct are:
- If there is already a job for master in queue there is no need to trigger a second one (different for feature branch)
- For master we need much less history of builds
- Perhaps different configuration of build/test/clean
Proposal
Additional configuration of Jenkins CI or perhaps support of variables for the jenkins job name.
Permissions and Security
Like Jenkins CI configuration
Documentation
What does success look like, and how can we measure that?
Links / references
https://forum.gitlab.com/t/integration-with-jenkins-different-job-for-master/23147
Edited by Jason Yavorska