JenkinsIcon indicating the project type

Jenkins

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

git project building twice every time new change committed

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: git-plugin
    • Labels:
      None
    • Environment:
      MacOS, Linux
    • Similar Issues:

      Description

      Running git-plugin 1.3.0, git-client-plugin 1.0.5, jenkins version 1.506

      Whenever I check in, my build will trigger twice (but only 2 times, never more than that). I've tried limiting to specific branches, and adding different refspecs, but nothing has seemed to work.

      I have attached 3 screenshots. The first is the build information page on the first build. Please note that it says, "2 times"

      The 2nd is the polling log for the first build.

      The 3rd is the polling log for the 2nd build.

      I find that if I watch the polling, the build does not seem to trigger right away and spends some time resetting itself in the quiet period. Once it triggers, it usually triggers with 2 builds to do right away, which can be viewed in the 4th picture.

        Attachments

          Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-30350 Jobs get triggered twice from polling git scm

          • Major - Major loss of function.
          • Open
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-30350 Jobs get triggered twice from polling git scm

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-16513 Duplicate builds being triggered upon github merges.

          • Major - Major loss of function.
          • Resolved

            Activity

            Ascending order - Click to sort in descending order
            8 older comments
            Hide
            Permalink
            sebastian_sl sebastian slutzky added a comment -

            I'm experiencing the same issue after the last Jenkins upgrade.

            • Git plugin: 2.4.4
            • Jenkins version: 2.7

            In my case, it is just polling to a normal (long lived, not recreated every time) github repo

            the symptoms are the same as described by Stefan Henning

            Show
            sebastian_sl sebastian slutzky added a comment - I'm experiencing the same issue after the last Jenkins upgrade. Git plugin: 2.4.4 Jenkins version: 2.7 In my case, it is just polling to a normal (long lived, not recreated every time) github repo the symptoms are the same as described by Stefan Henning
            Hide
            Permalink
            thuongshoo Shoo Yoo Yoon added a comment -

            My Jenkins sever is using mostly the latest version but the same issue. SCM polling is run every 15 minutes but everybuild takes about 2 hours. Two "pollingLog" pages are moslty the same except the started time.

            My Jenkins sever:

            • jenkins : 2.35
            • Git plugin: 3.0.1
            Show
            thuongshoo Shoo Yoo Yoon added a comment - My Jenkins sever is using mostly the latest version but the same issue. SCM polling is run every 15 minutes but everybuild takes about 2 hours. Two "pollingLog" pages are moslty the same except the started time. My Jenkins sever: jenkins : 2.35 Git plugin: 3.0.1
            Hide
            Permalink
            eyalzek Eyal Zekaria added a comment -

            I experience the same issue described in the original post. I've noticed that this behavior is only happening when the job is configured to build on merge to master. Our PR jobs do not have this issue at all.
            Using:

            • jenkins 2.7.4.4
            • github plugin 1.22.3
            • git plugin 2.6.0
            Show
            eyalzek Eyal Zekaria added a comment - I experience the same issue described in the original post. I've noticed that this behavior is only happening when the job is configured to build on merge to master. Our PR jobs do not have this issue at all. Using: jenkins 2.7.4.4 github plugin 1.22.3 git plugin 2.6.0
            Hide
            Permalink
            sobomax Maksym Sobolyev added a comment -

            Same here.

             

            Jenkins: 2.147

            github plugin: 1.29.3

            git client plugin: 2.7.3

            git plugin: 3.9.1

            Show
            sobomax Maksym Sobolyev added a comment - Same here.   Jenkins: 2.147 github plugin: 1.29.3 git client plugin: 2.7.3 git plugin: 3.9.1
            Hide
            Permalink
            wdf William F added a comment -

            I'm experiencing exactly the same thing as Eyal Zekaria – we get double (and sometimes triple) builds fairly frequently for our master branches, but never for PR branches.

             

            Jenkins: 2.150.1

            github plugin: 1.29.4

            git client plugin: 2.7.6

            git plugin: 3.9.3

            Show
            wdf William F added a comment - I'm experiencing exactly the same thing as Eyal Zekaria – we get double (and sometimes triple) builds fairly frequently for our master branches, but never for PR branches.   Jenkins: 2.150.1 github plugin: 1.29.4 git client plugin: 2.7.6 git plugin: 3.9.3

              People

              • Assignee:
                Unassigned
                Reporter:
                el_chapitan Marc Chapman
              • Votes:
                22 Vote for this issue
                Watchers:
                25 Start watching this issue

                Dates

                • Created:
                  Updated: