Status: Open (View Workflow)
The scm poll to trigger the build seem to only check the build, so if configuration is changed and the build is into an unsuccessful state, a manual trigger will not update the poll information. The poll should be done according to the lastest build no matter what the build results is (completed/incompleted/successful/failed...). Cause now you have to have a clean successful build to make the Build Triggers poll SCM work properly.
Jesse Glick made changes -
|Field||Original Value||New Value|
|Component/s||workflow-job-plugin [ 21716 ]|
|Component/s||pipeline [ 21692 ]|
|Component/s||scm-api-plugin [ 18054 ]|
|Issue Type||Bug [ 1 ]||Improvement [ 4 ]|
|Labels||Pipeline Polling SCM buildtriggerplugin||polling scm|
The current behavior is as designed: a failed build could mean that no checkout was performed, or that some were but others were not, etc. Currently it is up to you to get at least one unstable build before SCM triggers will resume.