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

multibranch pipeline job notified by stash, mutliple job/projects build

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Hi,

      we have a case where we receive a notifyCommit command from our Stash server for a specific repo/branch which triggers (seemingly random) builds for other jobs/repos as well. If we receive another notifyCommit within a few minutes all seems to work correctly, but after a while (>10 min), receiving another notifyCommit causes the same issues again.

      We see the following on all jobs that start building:

      [Tue Feb 21 15:22:43 UTC 2017] Received jenkins.plugins.git.GitSCMSource$ListenerImpl$1 UPDATED event from X.X.X.X ⇒ http://<domain>:55642/git/notifyCommit with timestamp Tue Feb 21 15:22:22 UTC 2017
 > git rev-parse --is-inside-work-tree # timeout=10
.....
Checking branch master
      'Jenkinsfile' found
Met criteria
Takeover for project-name » master by source #1 from source that no longer exists
Branch reopened: master (4171412e6dd9104cd760f575bf11ae74e0a32849)
Scheduled build for branch: master

      Everytime we see the following two confusing lines:

      Takeover for project-name » master by source #1 from source that no longer exists
      Branch reopened: master (4171412e6dd9104cd760f575bf11ae74e0a32849)

      We are 100% sure nothing changed for master and there is no need to schedule a build.

        Attachments

          Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-42236 SCMEventImpl should check isMatch() conditions in heads() method

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            markewaite Mark Waite added a comment -

            The message 

            Takeover for project-name » master by source #1 from source that no longer exists
Branch reopened: master (4171412e6dd9104cd760f575bf11ae74e0a32849)

            is not from the git plugin. Unfortunately, I don't know which plugin provides that message. My initial search attempts on GitHub did not locate that string, but I'm reasonably confident that the bug should not be assigned to the git plugin.

            Show
            markewaite Mark Waite added a comment - The message Takeover for project-name » master by source #1 from source that no longer exists Branch reopened: master (4171412e6dd9104cd760f575bf11ae74e0a32849) is not from the git plugin. Unfortunately, I don't know which plugin provides that message. My initial search attempts on GitHub did not locate that string, but I'm reasonably confident that the bug should not be assigned to the git plugin.
            Hide
            Permalink
            rolphh Rolph Haspers added a comment - - edited

            Mark Waite the issue seem to be caused by this change in december: https://github.com/jenkinsci/branch-api-plugin/commit/c3c431021debd74df0368d97ebfe66e2d3cd8381#diff-b347159a8a8075d4e700065f8668b804

            Show
            rolphh Rolph Haspers added a comment - - edited Mark Waite the issue seem to be caused by this change in december: https://github.com/jenkinsci/branch-api-plugin/commit/c3c431021debd74df0368d97ebfe66e2d3cd8381#diff-b347159a8a8075d4e700065f8668b804
            Hide
            Permalink
            stephenconnolly Stephen Connolly added a comment -

            This sounds like an exact duplicate of JENKINS-42236 which was fixed in https://github.com/jenkinsci/git-plugin/commit/59a826435ff7c8dfbd4c6739842c5b06dbcd337d

            If upgrading the git-plugin to 3.1.0 resolves the issue please close as a confirmed duplicate, otherwise re-open and we'll take a look see what is going on (but I would be exceedingly shocked if this is not JENKINS-42236)

            Show
            stephenconnolly Stephen Connolly added a comment - This sounds like an exact duplicate of JENKINS-42236 which was fixed in https://github.com/jenkinsci/git-plugin/commit/59a826435ff7c8dfbd4c6739842c5b06dbcd337d If upgrading the git-plugin to 3.1.0 resolves the issue please close as a confirmed duplicate, otherwise re-open and we'll take a look see what is going on (but I would be exceedingly shocked if this is not JENKINS-42236 )

              People

              Assignee:
              stephenconnolly Stephen Connolly
              Reporter:
              rolphh Rolph Haspers
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: