[
https://issues.jenkins-ci.org/browse/JENKINS-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Wolfgang resolved JENKINS-13514.
------------------------------------------
Resolution: Fixed
> Matrix Reloaded should trigger the same combination in downstream matrix job
> ----------------------------------------------------------------------------
>
> Key: JENKINS-13514
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13514
> Project: Jenkins
> Issue Type: Improvement
> Components: matrix-reloaded
> Affects Versions: current
> Reporter: Dirk Haun
> Assignee: Christian Wolfgang
> Priority: Minor
> Attachments: 01-jobA.png, 02-jobB.png
>
>
> When rebuilding parts of a matrix job (using the matrix reloaded plugin), the
> build will then trigger all downstream jobs. In our case, the downstream jobs
> are also matrix jobs and we would like that in this case, the downstream jobs
> are also "reloaded", i.e. only the parts that were rebuilt in the upstream
> job should be built there as well.
> To reproduce, I've used a setup that somewhat resembles what we have:
> - 2 matrix jobs, jobA and jobB
> - jobA has jobB as its downstream job
> - each job consists of a 3x3 matrix with the axis labelled "compiler" and
> "os" respectively
> - the compiler axis has values FORTE, GCC, MSC
> - the os axis has values solaris, linux, windows
> - the build step is just a echo "hello world"
> We're using the Parameterized Build plugin,
> http://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin, to
> trigger downstream builds but this can also be reproduced with the standard
> "Build other projects" option.
> The two screenshots show the matrix and which parts are supposed to be
> rebuild. The second screenshot shows that jobB, when triggered by rebuilding
> only parts of the jobA matrix, is actually building all 9 combinations, not
> just the 2 of the upstream job.
> P.S. I mentioned this problem at the Jenkins User Conference in Paris, in
> case you remember :)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
