-
New Feature
-
Resolution: Fixed
-
Major
-
None
There should be an option to create branch projects automatically wherever a Jenkinsfile is detected, yet suppress the automatic SCM trigger which fires when branch indexing detects a new branch head. Manual or other automatic scheduled builds should still be possible.
Needs to be supported as a configuration option at least at the level of a single multibranch project, or an organization folder. TBD whether there is a need to reinstate the built-in SCM trigger for certain branches, certain repos, etc.
- depends on
-
JENKINS-30206 Multibranch plugin: Modified properties do not propagate to existing branches
-
- Open
-
- is duplicated by
-
JENKINS-33909 Prevent automatic trigger of of jobs once scan has created them
-
- Resolved
-
- is related to
-
JENKINS-34725 Multibranch Plugin: Shouldn't run every branch on re-index
-
- Closed
-
-
JENKINS-64896 overrideIndexTriggers not respected on PRs
-
- Open
-
-
JENKINS-34005 Make WorkflowJob.triggers into a JobProperty
-
- Resolved
-
- relates to
-
JENKINS-45814 "Suppress automatic SCM triggering" prevents push notifications
-
- Closed
-
-
JENKINS-37220 Job DSL analogue of multibranch projects & organization folders
-
- Open
-
- links to
Also probably the initial build #1 should not be automatically scheduled with this option enabled, though that can cause problems when you want to have an automatic trigger set up via the properties step—without the initial build, there will be no job properties, preventing a declarative trigger from being “bootstrapped”. Various implications need to be studied.