Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Duplicate
-
Jenkins ver. 2.47
Git plugin: 3.0.5
Pipeline plugin: 2.5
Atlassian Stash: 3.11.4
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
-
JENKINS-42236 SCMEventImpl should check isMatch() conditions in heads() method
-
- Closed
-
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.