Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-48784

Workflow job doesn't update properly if you change a SCMStep polling from true to false

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • workflow-job-plugin
    • None
    • Jenkins 2.82
      workflow-job-plugin 2.15

      Workflow job doesn't update properly if you change a SCMStep polling from true to false.

      The polling baseline never gets reset in WorkflowJob. It's not persisted, so you can get around it by restarting the Jenkins server (not ideal).

      Repro Steps:

      1. Setup workflow job to run an SCMStep and setup SCM polling time interval.
        1. git(poll: true, changelog: true, ....)
      2. Run the workflow job.
        1. Polling log should show the SCM being checked
      3. Modify workflow job to set poll/changelog to false
        1. git(poll: false, changelog: false, ...)
      4. Submit a change to your SCM. It'll trigger even though you've disabled it.
        1. The polling log shows it checking that SCM even though you've disabled it.
        2. It's supposed to show "no polling baseline in ***" in the polling log when it's working

          [JENKINS-48784] Workflow job doesn't update properly if you change a SCMStep polling from true to false

          Andrew Bayer added a comment -

          Are you running a build after changing the Jenkinsfile to disable polling?

          Andrew Bayer added a comment - Are you running a build after changing the Jenkinsfile to disable polling?

          Michael Wong added a comment -

          Yes, it's still polling after running a build manually where polling is disabled.

          Michael Wong added a comment - Yes, it's still polling after running a build manually where polling is disabled.

          Cenk Tosun added a comment -

          I have the same problem here. Using pipeline jobs with multiple checkout of git repos.

          I am not sure what happens, but on every first build of the day and also in the course of the day, i get the message "no polling baseline in ***" on.

          as a result at least one new build although there have been no changes.

          that have led to an error so far:

          • changing branch will end up with polling in the old branch (i guess until the first successful build)
          • change/update of polling - end up with unnecessary builds
          • workspace clean-up (assumption) - end up with unnecessary builds

          And Idea or additional experiences?

          Cenk Tosun added a comment - I have the same problem here. Using pipeline jobs with multiple checkout of git repos. I am not sure what happens, but on every first build of the day and also in the course of the day, i get the message "no polling baseline in ***" on. as a result at least one new build although there have been no changes. that have led to an error so far: changing branch will end up with polling in the old branch (i guess until the first successful build) change/update of polling - end up with unnecessary builds workspace clean-up (assumption) - end up with unnecessary builds And Idea or additional experiences?

            Unassigned Unassigned
            michaelw Michael Wong
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: