-
Bug
-
Resolution: Not A Defect
-
Minor
-
None
-
Jenkins 2.150.2
branch-api-plugin 2.1.0
Pipeline Multibranch Plugin 2.20
Jenkins 2.150.3
branch-api-plugin 2.1.2
Pipeline Multibranch Plugin 2.20
I am using multibranch pipeline job.
After few upgrades, I've noticed that Property strategy -> Suppress automatic SCM triggering is shown as deprecated in existing jobs and I can't add it to new jobs.
Tested on different Jenkins instances with current / latest versions, still the same.
Not sure which plugin caused this change, so happy to add more info if needed.
- is related to
-
-
- Open
-
[JENKINS-56231] Suppress automatic SCM triggering is deprecated
Grigory Netsman
created issue -
Grigory Netsman
made changes -
| Summary | Original: suppress automatic scm triggering is deprecated | New: Suppress automatic SCM triggering is deprecated |
Grigory Netsman
made changes -
| Component/s | New: workflow-multibranch-plugin [ 21465 ] |
Andreas Sieferlinger
added a comment - We also experience this issue, and neither found a way to work around this?
Anybody has a suitable workaround or some more information on why this was removed at all?
Andreas Sieferlinger
added a comment - We also experience this issue, and neither found a way to work around this?
Anybody has a suitable workaround or some more information on why this was removed at all? 
Christian Ciach
added a comment - The deprecation is part of JENKINS-47859
The JavaDoc of the class `NoTriggerBranchProperty` says:
@deprecated Replaced by a named branch build strategy in the <code>basic-branch-build-strategies</code> plugin
Christian Ciach
added a comment - The deprecation is part of JENKINS-47859
The JavaDoc of the class `NoTriggerBranchProperty` says:
@deprecated Replaced by a named branch build strategy in the <code>basic-branch-build-strategies</code> plugin
Oleg Maki
added a comment - Could you please provide some sample how "Suppress automatic SCM triggering" could be achieved with "named branch build strategy"
Oleg Maki
added a comment - Could you please provide some sample how "Suppress automatic SCM triggering" could be achieved with "named branch build strategy" 
Mykola Ulianytskyi
added a comment - Not sure which plugin caused this change, so happy to add more info if needed.
Installation of plugin "Basic Branch Build Strategies" removes the property "Suppress automatic SCM triggering".
What is the alternative to deprecated property "Suppress automatic SCM triggering"?!
Mykola Ulianytskyi
added a comment - Not sure which plugin caused this change, so happy to add more info if needed.
Installation of plugin "Basic Branch Build Strategies" removes the property "Suppress automatic SCM triggering".
What is the alternative to deprecated property "Suppress automatic SCM triggering"?! Grigory Netsman
added a comment - I think the idea is to use Build Strategy -> Named branches -> Wildcard include/exclude -> Excludes *, that seem to be working for me
Grigory Netsman
added a comment - I think the idea is to use Build Strategy -> Named branches -> Wildcard include/exclude -> Excludes *, that seem to be working for me Mykola Ulianytskyi
added a comment - Thank you, gnetsman
It works for me too.
P.S. I excluded all branches in build strategy and tested pollSCM trigger in pipeline.
Result: Polling works even if branch was excluded. Good
Mykola Ulianytskyi
added a comment - Thank you, gnetsman
It works for me too.
P.S. I excluded all branches in build strategy and tested pollSCM trigger in pipeline.
Result: Polling works even if branch was excluded. Good
I just noticed this, too. I cannot find a suitable alternative. Please at least adjust the help-text to tell users what to do instead.
The main issue for me is the fact that Jenkins even triggers builds on branch-indexing when the build is parametrized. Of course, without parameters, these builds usually fail.