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

Repo Build Code Changes not Identified When Job Config is Modified

      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.

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

          Bahram Parsapour added a comment - - edited

          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:

          ...
          [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)

          Bahram Parsapour added a comment - - edited 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: ... [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)

            Unassigned Unassigned
            rejesi rejesi
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: