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

No changes detected by git

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: git-plugin
    • Labels:
      None
    • Environment:
      blueocean-git-pipeline:1.23.2
      blueocean-github-pipeline:1.23.2
      git:4.4.1
      git-client:3.4.2
      git-server:1.9
      github:1.31.0
      github-api:1.116
      github-branch-source:2.9.0

      git version 1.8.3.1
      Jenkins version 2.255
    • Similar Issues:

      Description

      We started to randomly run into the following issue. Bitbucket webhook sends an update to Jenkins multibranch pipeline, but pipeline doesn't schedule a build because it detects no changes, even though the commit that triggered UPDATE is in bitbucket.

      [Thu Sep 10 13:21:01 EDT 2020] Received jenkins.plugins.git.GitSCMSource$ListenerImpl$1 UPDATED event from x.x.x.x ⇒ http://host:port/git/notifyCommit with timestamp Thu Sep 10 13:21:01 EDT 2020
      ...

      git ls-remote -h ssh://user@bitbucket/a/repo.git # timeout=10
      ...
      Checking branches...
      Checking branch release/1.247.0
      ‘Jenkinsfile’ found
      Met criteria
      No changes detected: release/1.247.0 (still at cc0f29d85ec79db0ef7dc798c8a4e9e2fe0ee410)

      There is another commit that exists after [ cc0f29d85ec79db0ef7dc798c8a4e9e2fe0ee410 ], and i can see it with git ls-remote. If I do "Scan Multibranch Pipeline Now" it will pick up the change.
      Sounds like a timing issue.

        Attachments

          Activity

          Hide
          markewaite Mark Waite added a comment -

          Does it behave differently if the branch name is given as origin/release/1.247.0 rather than release/1.247.0? I believe there was an issue reported for branch names that contain a single slash '/' with the left side of the slash not being a remote name.

          Show
          markewaite Mark Waite added a comment - Does it behave differently if the branch name is given as origin/release/1.247.0 rather than release/1.247.0 ? I believe there was an issue reported for branch names that contain a single slash '/' with the left side of the slash not being a remote name.
          Hide
          adpoint72 Alex Dobkin added a comment -

          This is triggered by Bitbucket webhook, not sure how would you make Bitbucket webhook provide a different branch name.

          BTW this doesn't happen every time, it happens randomly.  For some reason it started to occur at a higher frequency now.  (repo got larger, more tags, etc?)

          Show
          adpoint72 Alex Dobkin added a comment - This is triggered by Bitbucket webhook, not sure how would you make Bitbucket webhook provide a different branch name. BTW this doesn't happen every time, it happens randomly.  For some reason it started to occur at a higher frequency now.  (repo got larger, more tags, etc?)
          Hide
          markewaite Mark Waite added a comment -

          I believe the Bitbucket webhook may be passing the branch name as an argument when it calls Jenkins. If so, then there may be a location in Bitbucket where you can specify the values of web hook arguments.

          Show
          markewaite Mark Waite added a comment - I believe the Bitbucket webhook may be passing the branch name as an argument when it calls Jenkins. If so, then there may be a location in Bitbucket where you can specify the values of web hook arguments.
          Hide
          adpoint72 Alex Dobkin added a comment -

          there is 1 webhook for git repo, not 1 for branch, don't see how it would be possible to set it on the webhook.

          Show
          adpoint72 Alex Dobkin added a comment - there is 1 webhook for git repo, not 1 for branch, don't see how it would be possible to set it on the webhook.
          Hide
          adpoint72 Alex Dobkin added a comment -

          we still run into this issue.  this could be just a coincidence but repos with more branches seem to be more susceptible to this behavior.  Mark Waite any clues?

          Show
          adpoint72 Alex Dobkin added a comment - we still run into this issue.  this could be just a coincidence but repos with more branches seem to be more susceptible to this behavior.  Mark Waite any clues?
          Hide
          markewaite Mark Waite added a comment -

          No clues from me Alex Dobkin, sorry

          Show
          markewaite Mark Waite added a comment - No clues from me Alex Dobkin , sorry

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            adpoint72 Alex Dobkin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: