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

GitPlugin | Concurrent builds are serialized when publishing

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      We're using a parameterized job, so that several branches of the same repo can be built concurrently. The job is configured to add a tag to the repo as a post-build action.
      When we have several jobs running, they sometimes get stuck: even though a job is finished, it "waits" for the previou jobs to finish. The message is:

      Git Publisher is waiting for a checkpoint on <job_name> #<prev_build_number>

      This causes a chain reaction, whereby several jobs are just hanging.

      I saw a similar issue in JENKINS-9913, but that seems to have been resolved, and it pertained to JUnit.

        Attachments

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-9913 Not obvious why some post-build tasks enforce serial behavior even when builds are concurrent

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link PR-645

            Activity

            Ascending order - Click to sort in descending order
            4 older comments
            Hide
            Permalink
            rejeeshchandran Rejeesh Chandran added a comment -

            We are getting the same issue but with Memory Map Publisher plugin.

            Memory Map Publisher is waiting for a checkpoint on <Job Name> #<prev_build_number>

            If the previous job is taking too much time or stuck then then next job will also be taking time or stuck at this point.

            Show
            rejeeshchandran Rejeesh Chandran added a comment - We are getting the same issue but with Memory Map Publisher plugin. Memory Map Publisher is waiting for a checkpoint on <Job Name> #<prev_build_number> If the previous job is taking too much time or stuck then then next job will also be taking time or stuck at this point.
            Hide
            Permalink
            pjaiswal Pragya Jaiswal added a comment -

            Did anyone find a resolution or workaround to this problem?

            Show
            pjaiswal Pragya Jaiswal added a comment - Did anyone find a resolution or workaround to this problem?
            Hide
            Permalink
            moshe_zvi Moshe Zvi added a comment -

            It's always a bad sign when you search for a bug and realize you had already reported it two years ago :/

            One more thing: in the gitlab plugin, they resolved a similar issue:

            https://github.com/jenkinsci/gitlab-plugin/pull/397

            Maybe this can help?

            Show
            moshe_zvi Moshe Zvi added a comment - It's always a bad sign when you search for a bug and realize you had already reported it two years ago :/ One more thing: in the gitlab plugin, they resolved a similar issue: https://github.com/jenkinsci/gitlab-plugin/pull/397 Maybe this can help?
            Hide
            Permalink
            markewaite Mark Waite added a comment -

            Fixed in the master branch, will be included in git plugin 4.0.0

            Show
            markewaite Mark Waite added a comment - Fixed in the master branch, will be included in git plugin 4.0.0
            Hide
            Permalink
            markewaite Mark Waite added a comment -

            Included in git plugin 4.0.0 released Nov 2, 2019

            Show
            markewaite Mark Waite added a comment - Included in git plugin 4.0.0 released Nov 2, 2019

              People

              Assignee:
              markewaite Mark Waite
              Reporter:
              moshe_zvi Moshe Zvi
              Votes:
              3 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: