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

Polling SCM results in infinite builds after pushing changes on GITLab repository

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Blocker
    • Resolution: Unresolved
    • Component/s: git-plugin
    • Labels:
      None
    • Environment:
      Jenkins 1.638
      Git plugin 2.4.0
      Java 1.7.0_65-b19
    • Similar Issues:

      Description

      We have a project that get code from GITLab repository, performs build and then pushes back updates on the same branch. The push is done with a specific user and we add this user to the list of "Polling ignore commits from certain users".

      We added also a push web-hook to the Gitlab project that uses a URL similar to this one described in Git Plugin to trigger the job SCM Poll:
      http://yourserver/git/notifyCommit?url=<URL of the Git repository>

      After pushing an update with a normal user the web-hook is triggered and the poll starts and the job builds, the job then pushes the results back to the branch, after which the job is triggered again, but sometimes the polling log is shown correctly and sometimes the polling log not showing.

      When the polling log shows correctly, the excluded user filter is applied, but if the polling log does not appear the excluded user filter is not applied and then the building enter in an infinite loop since it continue pushing updates and the same state persists (poll log does not show any text although the build appears to be "Started by an SCM change")

        Attachments

        1. 1.png
          1.png
          5 kB
        2. 2.png
          2.png
          38 kB

          Issue Links

            Activity

            Hide
            levelik Iulian Petcu added a comment -

            This issue occurs randomly and the only fix that I've found was to enable advance clone behaviours - shallow clone with depth 0.

            Show
            levelik Iulian Petcu added a comment - This issue occurs randomly and the only fix that I've found was to enable advance clone behaviours - shallow clone with depth 0.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              ayaserry Aya Serry
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: