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

git builds are never triggered if quiet period > pooling interval

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • git-plugin
    • None
    • Jenkins 1.421 + Git plugin 1.1.10

    Description

      This is a problem already met in SVN and others providers several years ago.
      If the quiet period is > to the pooling interval the build never starts because the quiet period is setup to its max each time the pooling is done

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-2180 Quiet period keeps running without building

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            aheritier Arnaud Héritier added a comment -

            1.1.11 had the same problem but upgrading to 1.425-SNAPSHOT seems to solve the issue. Isn't it strange ?

            aheritier Arnaud Héritier added a comment - 1.1.11 had the same problem but upgrading to 1.425-SNAPSHOT seems to solve the issue. Isn't it strange ?
            aheritier Arnaud Héritier added a comment -

            Ok, I perhaps know how I solved the problem.
            I changed the job configuration not clone the repository on the root of the workspace but on a subdirectory (to be able to ask to git to do a cleanup without loosing my local maven repository).

            aheritier Arnaud Héritier added a comment - Ok, I perhaps know how I solved the problem. I changed the job configuration not clone the repository on the root of the workspace but on a subdirectory (to be able to ask to git to do a cleanup without loosing my local maven repository).
            erikengerd erikengerd added a comment -

            the issue is still there in 1.424.

            erikengerd erikengerd added a comment - the issue is still there in 1.424.
            markewaite Mark Waite added a comment - - edited

            Using git plugin 2.3.1, git client plugin 1.12.0, and Jenkins 1.580.2-RC, I am able to duplicate this bug.

            I took the following steps in my attempt to duplicate the bug:

            1. Define a new freestyle project with a quiet period of 130 seconds
            2. Use git as the SCM system, and set a polling interval once a minute
            3. Confirm that the initial polling detects a build is needed
            4. Confirm that the initial build starts about 2 minutes after the first poll
            5. Pushed a change to the repository
            6. Confirm the polling detects change and schedules a build
            7. Confirm that the quiet period decrements from 2 minutes 10 seconds to about 1 minute 10 seconds, then increases again to 2 minutes 10 seconds. The scheduled build never runs even though changes are detected
            markewaite Mark Waite added a comment - - edited Using git plugin 2.3.1, git client plugin 1.12.0, and Jenkins 1.580.2-RC, I am able to duplicate this bug. I took the following steps in my attempt to duplicate the bug: Define a new freestyle project with a quiet period of 130 seconds Use git as the SCM system, and set a polling interval once a minute Confirm that the initial polling detects a build is needed Confirm that the initial build starts about 2 minutes after the first poll Pushed a change to the repository Confirm the polling detects change and schedules a build Confirm that the quiet period decrements from 2 minutes 10 seconds to about 1 minute 10 seconds, then increases again to 2 minutes 10 seconds. The scheduled build never runs even though changes are detected

            People

              Unassigned Unassigned
              aheritier Arnaud Héritier
              Votes:
              5 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated: