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.

          [JENKINS-45996] Pipeline Poll SCM only check last successful

          Jesse Glick added a comment -

          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.

          Jesse Glick added a comment - 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.

            Unassigned Unassigned
            jerome_godbout Jerome Godbout
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: