[JIRA] (JENKINS-14855) Repo Build Code Changes not Identified When Job Config is Modified

[bahram.parsap...@dynatrace.com (JIRA)]

Title: Message Title

Bahram Parsapour commented on JENKINS-14855   Re: Repo Build Code Changes not Identified When Job Config is Modified We also have this kind of problem and see a lot of events like the following below in our multi branch builds - where job configurations are modified from time to time: ... [Wed Feb 22 22:38:25 CET 2017] Received jenkins.plugins.git.GitSCMSource$ListenerImpl$1 UPDATED event from <xxx.xx.xxx.xx> ⇒ http://<dns>:41138/git/notifyCommit with timestamp Wed Feb 22 22:37:10 CET 2017 > git rev-parse --is-inside-work-tree # timeout=10 ... Checking branch master ‘Jenkinsfile’ found Met criteria Takeover for Synthetic » Builds » common » master by source #1 from source that no longer exists Branch reopened: master (fee002ae94cd1d25ee9a542f5abc049150d109fa) Scheduled build for branch: master [Wed Feb 22 22:38:26 CET 2017] jenkins.plugins.git.GitSCMSource$ListenerImpl$1 UPDATED event from <xxx.xx.xxx.xx> ⇒ http://<dns>:41138/git/notifyCommit with timestamp Wed ... The following log output is extremely confusing from our point of view: Takeover for Synthetic » Builds » common » master by source #1 from source that no longer exists Branch reopened: master (fee002ae94cd1d25ee9a542f5abc049150d109fa) Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.