[
https://issues.jenkins-ci.org/browse/JENKINS-12778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159113#comment-159113
]
Thorsten Möllers commented on JENKINS-12778:
--------------------------------------------
The easiest way to implement this without breaking the compatibility for older
configurations might be to let the existing touchstone config field
(touchStoneCombinationFilter) accept several semicolon separated expressions,
and to split it up in MatrixBuild.java in doRun. I would assume that there is
currently no valid use case for semicolons in this field, so it should not
break compatibility with existing project configurations.
It would probably look nicer to have as similar interface as is used for the
axes, but I'm not familiar enough with Jenkins to be sure how to implement it
without causing compatibility problems with existing projects.
Is there any chance to get the first proposal (semicolon separated touchstones)
accepted? I would like to start implementing, but if this proposal looks too
messy to stand a chance I would not want to waste my time...
> Extend touchstone functionality to allow for multiple touchstones
> -----------------------------------------------------------------
>
> Key: JENKINS-12778
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12778
> Project: Jenkins
> Issue Type: New Feature
> Components: matrix
> Reporter: Thorsten Möllers
>
> Since I have to support a constantly/rapidly changing set of branches, each
> supporting a couple of platforms, I want to be able to have only one matrix
> per branch job to do all builds/tests per branch. To achieve this
> efficiently, I need to be able to configure the matrix job to
> 1. build main targets for all supported platforms
> 2. If 1 succeeds, run unit test for all supported platforms
> 3. If 2 succeeds, build additional test tools for more extensive tests
> 4. If 3 succeeds, run tests for all supported platforms
> For this I need to be able to define different touchstones for each of the
> steps.
--
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
