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

URL copy polling compares to workspace instead of previous poll, causing long quiet time problems

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • urlscm-plugin
    • None

      This is related to JENKINS-2180.

      I'm using the URL Copy SCM, polling every 5 minutes for changes. I wanted to trigger the build on updates to the url(s), but not until they've settled down. To this end, I use the quiet period functionality. I set the quiet period to 315 seconds (15 seconds more than my polling interval). However, since enabling this, no builds have happened at all. This seems to be because when it polls, it compares to the workspace rather than the results of the preceding polling.

          [JENKINS-9191] URL copy polling compares to workspace instead of previous poll, causing long quiet time problems

          Soren Hansen added a comment -

          fwiw, I've managed to work around it by splitting this job into two:

          • One that has no quiet period, does the polling, and triggers the "real" job as a downstream job.
          • The "real" job which does all the work. It has a quiet period defined which is somewhat longer than the polling job's polling interval.

          This way, the polling job doesn't need to differentiate between what it saw when it last polled and what is in its workspace, and the "real" job can take care of maintaining the quiet period.

          This seems to do what I want, but of course the bug is still accurate. I'm just mentioning this workaround to help out others in a similar situation.

          Soren Hansen added a comment - fwiw, I've managed to work around it by splitting this job into two: One that has no quiet period, does the polling, and triggers the "real" job as a downstream job. The "real" job which does all the work. It has a quiet period defined which is somewhat longer than the polling job's polling interval. This way, the polling job doesn't need to differentiate between what it saw when it last polled and what is in its workspace, and the "real" job can take care of maintaining the quiet period. This seems to do what I want, but of course the bug is still accurate. I'm just mentioning this workaround to help out others in a similar situation.

            dfabulich dfabulich
            soren Soren Hansen
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: