[JIRA] (JENKINS-14855) Repo Build Code Changes not Identified When Job Config is Modified
Title: Message Title Nicolas De Loof assigned an issue to Unassigned Jenkins / JENKINS-14855 Repo Build Code Changes not Identified When Job Config is Modified Change By: Nicolas De Loof Assignee: Nicolas De Loof Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
[JIRA] (JENKINS-14855) Repo Build Code Changes not Identified When Job Config is Modified
Title: Message Title Bahram Parsapour updated an issue Jenkins / JENKINS-14855 Repo Build Code Changes not Identified When Job Config is Modified Change By: Bahram Parsapour Component/s: multi-branch-project-plugin 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.
[JIRA] (JENKINS-14855) Repo Build Code Changes not Identified When Job Config is Modified
Title: Message Title
Bahram Parsapour edited a comment on JENKINS-14855
Re: Repo Build Code Changes not Identified When Job Config is Modified
We also have somehow a similar problem and see a lot of events - every 10 to 30 minutes - like the following below in our *multibranch builds* - where job configurations are modified from time to time:{code}...[Wed Feb 22 22:38:25 CET 2017] Received jenkins.plugins.git.GitSCMSource$ListenerImpl$1 UPDATED event from ⇒ http://: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’ foundMet criteriaTakeover for Synthetic » Builds » common » master by source #1 from source that no longer existsBranch 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 ⇒ http://:41138/git/notifyCommit with timestamp Wed ...{code}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.
[JIRA] (JENKINS-14855) Repo Build Code Changes not Identified When Job Config is Modified
Title: Message Title
Bahram Parsapour edited a comment on JENKINS-14855
Re: Repo Build Code Changes not Identified When Job Config is Modified
We also have this kind of somehow a similar problem and see a lot of events like the following below in our * multi branch multibranch builds* - where job configurations are modified from time to time:{code}...[Wed Feb 22 22:38:25 CET 2017] Received jenkins.plugins.git.GitSCMSource$ListenerImpl$1 UPDATED event from ⇒ http://: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’ foundMet criteriaTakeover for Synthetic » Builds » common » master by source #1 from source that no longer existsBranch 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 ⇒ http://:41138/git/notifyCommit with timestamp Wed ...{code}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.
[JIRA] (JENKINS-14855) Repo Build Code Changes not Identified When Job Config is Modified
Title: Message Title Bahram Parsapour updated an issue Jenkins / JENKINS-14855 Repo Build Code Changes not Identified When Job Config is Modified Change By: Bahram Parsapour Attachment: Scan Multibranch.png 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.
[JIRA] (JENKINS-14855) Repo Build Code Changes not Identified When Job Config is Modified
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 ⇒ http://: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 ⇒ http://: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 "Jenk
[JIRA] (JENKINS-14855) Repo Build Code Changes not Identified When Job Config is Modified
rejesi created JENKINS-14855 Repo Build Code Changes not Identified When Job Config is Modified Issue Type: Bug Assignee: Nicolas De Loof Components: git, repo Created: 17/Aug/12 7:57 PM Description: It seems that every time a build job configuration is modified, the code list changes cannot be identified for the first build after the modification. The Jenkins repo plugin seems to be failing to properly parse and record all the changes that trigger a build. Either that or not all commits are showing up in the log In place of changes, the message 'Failed to determine' is displayed with a link to the log. Looking at the log does not reveal any errors or stack traces. Environment: Linux RHEL server Linux Ubuntu slave agents Linux RHEL slave agents Jenkins 1.472 Repo 1.2.1 Git 1.1.21 Project: Jenkins Labels: plugin configuration jenkins Priority: Major Reporter: rejesi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
