• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • matrix-project-plugin
    • None

      I have a matrix multi-configuration project configured to build on GitHub Pull Request. When an update commit comes in to the branch, it's properly kicking off a build in Jenkins. The master build properly displays the commits on the branch. Example:

      Build #12 (Jul 24, 2015 4:56:41 PM)
      
      Changes
      1. something (commit: <commit1>) (detail)
      2. something else (commit: <commit2>) (detail)
      3. another thing (commit: <commit3>) (detail)
      	
      GitHub pull request #1234 of commit <commit3>, no merge conflicts.
      
      Git Revision: <commit3>, detached
      

      When the sub-job kicks off within the matrix however, it doesn't get the latest commit. Example:

      Build 1.7.8 (Jul 24, 2015 4:56:41 PM)
      
      Changes
      something (detail)
      something else (detail)
      	
      Started by upstream project myproject build number 12
      originally caused by:
      
      GitHub pull request #1234 of commit <commit3>, no merge conflicts.
      
      Git Revision: <commit2>, detached
      

      Notice how the sub-job includes the GitHub Pull Request Builder message with the updated commit but git checks out a revision behind.

          [JENKINS-29625] Matrix job updates don't see latest commit

          There are no comments yet on this issue.

            kohsuke Kohsuke Kawaguchi
            mattlqx Matt Kulka
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: