[JIRA] (JENKINS-56231) Suppress automatic SCM triggering is deprecated

29 views
Skip to first unread message

gnetsman@gmail.com (JIRA)

unread,
Feb 21, 2019, 5:06:01 AM2/21/19
to jenkinsc...@googlegroups.com
Grigory Netsman updated an issue
 
Jenkins / Bug JENKINS-56231
Suppress automatic SCM triggering is deprecated
Change By: Grigory Netsman
Summary: suppress Suppress automatic scm SCM triggering is deprecated
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

gnetsman@gmail.com (JIRA)

unread,
Feb 22, 2019, 2:10:02 AM2/22/19
to jenkinsc...@googlegroups.com
Grigory Netsman updated an issue
Change By: Grigory Netsman
Component/s: workflow-multibranch-plugin

christian.ciach@gmail.com (JIRA)

unread,
Feb 25, 2019, 4:59:02 AM2/25/19
to jenkinsc...@googlegroups.com
Christian Ciach commented on Bug JENKINS-56231
 
Re: Suppress automatic SCM triggering is deprecated

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.

christian.ciach@gmail.com (JIRA)

unread,
Feb 25, 2019, 5:35:02 AM2/25/19
to jenkinsc...@googlegroups.com
Christian Ciach edited a comment on Bug JENKINS-56231
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.

christian.ciach@gmail.com (JIRA)

unread,
Feb 25, 2019, 5:35:02 AM2/25/19
to jenkinsc...@googlegroups.com

irc@webratz.de (JIRA)

unread,
Mar 4, 2019, 8:47:06 AM3/4/19
to jenkinsc...@googlegroups.com

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@gmail.com (JIRA)

unread,
Mar 4, 2019, 9:08:02 AM3/4/19
to jenkinsc...@googlegroups.com

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

 

omakolegmaki@gmail.com (JIRA)

unread,
Mar 5, 2019, 6:12:02 AM3/5/19
to jenkinsc...@googlegroups.com

Could you please provide some sample how "Suppress automatic SCM triggering" could be achieved with "named branch build strategy"

lystor@gmail.com (JIRA)

unread,
Mar 6, 2019, 9:01:02 AM3/6/19
to jenkinsc...@googlegroups.com

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"?!

gnetsman@gmail.com (JIRA)

unread,
Mar 6, 2019, 9:18:03 AM3/6/19
to jenkinsc...@googlegroups.com

I think the idea is to use Build Strategy -> Named branches -> Wildcard include/exclude -> Excludes *, that seem to be working for me

lystor@gmail.com (JIRA)

unread,
Mar 6, 2019, 9:55:14 AM3/6/19
to jenkinsc...@googlegroups.com

Thank you, Grigory Netsman

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

lystor@gmail.com (JIRA)

unread,
Mar 6, 2019, 9:55:16 AM3/6/19
to jenkinsc...@googlegroups.com

gnetsman@gmail.com (JIRA)

unread,
Mar 6, 2019, 12:07:03 PM3/6/19
to jenkinsc...@googlegroups.com
Grigory Netsman resolved as Not A Defect
 
Change By: Grigory Netsman
Status: Open Resolved
Resolution: Not A Defect

esaad91@gmail.com (JIRA)

unread,
Apr 6, 2019, 12:48:02 PM4/6/19
to jenkinsc...@googlegroups.com
Esaad Afaque commented on Bug JENKINS-56231
 
Re: Suppress automatic SCM triggering is deprecated

I have noticed the same on my end too. Compared it to and older version of the Branch API plugin (2.0.20) and it had this option. 

This is a bummer because my team has been heavily reliant on this feature. 

esaad91@gmail.com (JIRA)

unread,
Apr 7, 2019, 6:10:03 PM4/7/19
to jenkinsc...@googlegroups.com

> Installation of plugin "Basic Branch Build Strategies" removes the property "Suppress automatic SCM triggering".

 

This helped me. All I had to do was disable the plugin and the Suppress option came back again. 

gena01@gmail.com (JIRA)

unread,
May 2, 2019, 7:51:02 PM5/2/19
to jenkinsc...@googlegroups.com

I know that the option is deprecated, however I am sorta stuck. We are using Github Organization type jobs and are trying to run "master" branch builds nightly instead of continually. I see no clean way to implement this with the current API. 

I have opened https://issues.jenkins-ci.org/browse/JENKINS-55519 in January for this. 

chai.bapat@gmail.com (JIRA)

unread,
Mar 9, 2020, 7:06:04 PM3/9/20
to jenkinsc...@googlegroups.com

Even I am facing similar issue. I have disabled GitHub WebHook that points to Jenkins Server because I want GitHub WebHook to point to a Lambda function. My lambda function filters Webhooks events and only when a specific comment is made on a PR I want to trigger a build on Jenkins. Unfortunately, after disabling the Webhook that points to jenkins directly, PR branches aren't being discovered and hence I am unable to trigger build on PR branches. I can resolve this problem by re-enabling the GitHub WebHook that points to Jenkins Server but disabling "Suppress automatic SCM triggering". Unfortunately I can't find that anymore on Jenkins Configure due to updates. How should I go about? I want Jenkins to discover branches but not trigger builds on its own.

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages