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

Jobs trigger continually even though there are no changes due to git repository being "corrupt"

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Blocker
    • Resolution: Unresolved
    • Component/s: git-plugin
    • Labels:
      None
    • Similar Issues:

      Description

      There is a problem with the git polling mechanism which is causing all our jobs to kick themselves off continually. This happens at random times and just fixes itself, but is causing us all sorts of problems due to the large number of builds triggered.

      This is an example of the git polling log:

       
      Started on 28-Oct-2011 03:20:22
      Using strategy: Default
      [poll] Last Build : #480
      [poll] Last Built Revision: Revision abcb8a2492b390521e0c720f96f66a88eae09f18 (origin/master)
      Workspace has a .git repository, but it appears to be corrupt.
      No Git repository yet, an initial checkout is required
      Done. Took 0.26 sec
      Changes found
      

      This is caused when a "git rev-parse --verify HEAD" fails for some reason, but there is no logging to help in what might have gone wrong. It looks like the try/catch around the validateRevision line is too simplistic and the cause of the exception should be considered before returning false.

        Attachments

          Activity

          Hide
          seanf Sean Flanigan added a comment -

          It seems that JGit was later disabled by default in git-client-plugin 1.0.5 because of problems with JGit.

          Is there a solution for this continual trigger problem when using git cli?

          Show
          seanf Sean Flanigan added a comment - It seems that JGit was later disabled by default in git-client-plugin 1.0.5 because of problems with JGit. Is there a solution for this continual trigger problem when using git cli?
          Hide
          olivergondza Oliver Gondža added a comment -

          Reopening the issue as JGit has problems on its own

          Show
          olivergondza Oliver Gondža added a comment - Reopening the issue as JGit has problems on its own
          Hide
          npsullia Narayana katooru added a comment - - edited

          Noticed  this on my jenkins. Is this still open?

          Show
          npsullia Narayana katooru added a comment - - edited Noticed  this on my jenkins. Is this still open?
          Hide
          chandramuralis Murali Srinivasan added a comment -

          It is funny that this issue still exists after 8 years.

          Show
          chandramuralis Murali Srinivasan added a comment - It is funny that this issue still exists after 8 years.
          Hide
          markewaite Mark Waite added a comment -

          Murali Srinivasan I'm happy to consider a pull request from someone with tests that show the problem, code changes to resolve the problem, and a detailed explanation of the root cause of the problem. I've not encountered this problem in my use of the git plugin.

          Show
          markewaite Mark Waite added a comment - Murali Srinivasan I'm happy to consider a pull request from someone with tests that show the problem, code changes to resolve the problem, and a detailed explanation of the root cause of the problem. I've not encountered this problem in my use of the git plugin.

            People

            • Assignee:
              Unassigned
              Reporter:
              james_cookie James Cook
            • Votes:
              18 Vote for this issue
              Watchers:
              30 Start watching this issue

              Dates

              • Created:
                Updated: