[
https://issues.jenkins-ci.org/browse/JENKINS-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162380#comment-162380
]
Lars Kruse commented on JENKINS-13514:
--------------------------------------
Right - I makes sense.
What we'll do is that we will not require the axises and their values to be a
"perfect match" but instead we will simply analyze which one of the reloaded
combinations that makes sense in the context of the down-stream build - the
ones that do will be reloaded, the rest will be ignored.
If nothing makes sense - nothing will be build.
The consequence of this is that a reloaded up-stream build could trigger a
down-stream build, that potentially does nothing at all. This may be right in
your context, but it's different from the way the plugin behaves today, and in
order to make the behavior backwards compliant we intend to set a checkbox on
the reloaded plugin, marking if down-stream builds should run in reloaded
"mode" too - or not.
Based on this revised design I'd like to raise the estimate with 4 hrs to a
total of 20 hrs all in all - including 12 month support of this new feature.
What do you think?
> 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
> 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
