[
https://issues.jenkins-ci.org/browse/JENKINS-12778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159918#comment-159918
]
dogfood commented on JENKINS-12778:
-----------------------------------
Integrated in !http://ci.jenkins-ci.org/images/16x16/yellow.png!
[jenkins_main_trunk #1576|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1576/]
[FIXED JENKINS-12778] this commit and previous 2 commits (Revision
7e2500c7d38ccf3b4944013afd11b75aa8c268ea)
Result = UNSTABLE
Kohsuke Kawaguchi :
[7e2500c7d38ccf3b4944013afd11b75aa8c268ea|https://github.com/jenkinsci/jenkins/commit/7e2500c7d38ccf3b4944013afd11b75aa8c268ea]
Files :
* changelog.html
> 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
> Attachments: test_jenkins-12778_jobs.tar, test_jenkins-12778_jobs.tar
>
>
> 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
