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

child jobs of matrix builds do not use svn revision from parent

      Child builds of matrix jobs should use the same subversion revision as the parent job to ensure consistent builds across axes.

      An example of where this doesn't happen: I use the parameterized-trigger plugin to pass the subversion revision from an upstream build job to a downstream matrix job.

      While the parent matrix build correctly picks the revision, the child builds just use the HEAD revision instea,

          [JENKINS-16753] child jobs of matrix builds do not use svn revision from parent

          Chris Withers created issue -

          cjo9900 added a comment -

          Might be related to JENKINS-14619

          And issue may occur where the Revision action is created in the parent but when passed to child jobs there have been additional commits during the checkout/update of the parent.

          cjo9900 added a comment - Might be related to JENKINS-14619 And issue may occur where the Revision action is created in the parent but when passed to child jobs there have been additional commits during the checkout/update of the parent.
          cjo9900 made changes -
          Link New: This issue is related to JENKINS-14619 [ JENKINS-14619 ]
          Jenkins IRC Bot made changes -
          Component/s New: matrix-project [ 18765 ]
          Component/s Original: matrix [ 15501 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 147580 ] New: JNJira + In-Review [ 176948 ]

            Unassigned Unassigned
            cjw296 Chris Withers
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: