|
||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||
- [JIRA] (JENKINS-14619) Matrix problem with ... [email protected] (JIRA)
- [JIRA] (JENKINS-14619) Matrix problem ... [email protected] (JIRA)
- [JIRA] (JENKINS-14619) Matrix problem ... [email protected] (JIRA)
- [JIRA] (JENKINS-14619) Matrix problem ... [email protected] (JIRA)
- [JIRA] (JENKINS-14619) Matrix problem ... [email protected] (JIRA)
- [JIRA] (JENKINS-14619) Matrix problem ... [email protected] (JIRA)
- [JIRA] (JENKINS-14619) Matrix problem ... [email protected] (JIRA)
- [JIRA] (JENKINS-14619) Matrix problem ... [email protected] (JIRA)
- [JIRA] (JENKINS-14619) Matrix problem ... [email protected] (JIRA)
- [JIRA] (JENKINS-14619) Matrix problem ... [email protected] (JIRA)

This is a problem with all actions that should be passed to the matrix configurations.
See mailing list item
https://groups.google.com/d/topic/jenkinsci-dev/h3TMwZ-qmDQ/discussion
I would propose adding all actions from parent build to the all of the configurations,
but are there any issues doing this?
I.e. actions should not be passed on.(MatrixSubsetAction in parameterized-trigger)
So should there be an interface that actions implement to indicate that they are passed from the parent to the configurations?
that the Matrix configuration can use to filter the actions passed to it.
Or are there any better suggestions?
[1] https://issues.jenkins-ci.org/browse/JENKINS-14619
[2] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/matrix/MatrixConfiguration.java#L358
[3] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/matrix/DefaultMatrixExecutionStrategyImpl.java#L200