Just knocked up an extension to the parameterized trigger plugin that will 
allow you to pass the inverse of what is build to a triggered job.
If this parameter is added to a Matrix build it will get the filter passed 
into it and then inverts the filter (makes it "!(<original filter>)" ) 
before passing to the triggered project matrix.

Note if no filter is passed in to the build then there will be no 
downstream filter created.
You can also request it to get the filter from the default config on in the 
project if no filter was passed in.

If this is useful for other people, 
can you add a request to the Issue tracker for the Parameterized trigger 
component issues.jenkins-ci.org requesting it.
and I might finish the test cases off and promote to the Jenkins wiki and 
repo.

The source can be found at 
https://github.com/cjo9900/inverse-matrix-subset-parameter-plugin

And the hpi plugin should be available at 
https://buildhive.cloudbees.com/job/cjo9900/job/inverse-matrix-subset-parameter-plugin/1/org.jenkins-ci.plugins$inverse-matrix-subset-parameter/




On Monday, 28 January 2013 09:05:30 UTC, JKett wrote:
>
> Hello, 
>
> I'm trying to set up a build pipeline. Therefore I have one job (pipe 
> starter) which monitors a repository for source code changes, and two 
> identical matrix jobs (priority and regular build) which build the 
> repository in different chroot environments. The priority matrix job gets 
> triggered by the pipe starter job via the 'Parameterized Trigger Plugin'. 
> I use the 'restrict to subset' option to build in only one environment 
> (combination of ubuntu version & architecture).
> After a successful priority build I would like to trigger the regular 
> build job to build the repository as well in all left environments.
> Now my question: Is it possible to get the triggering combination filter 
> in the priority job, negate it and use if as subset filter for the regular 
> build job? Maybe with a groovy script? Or exists already a variable which 
> holds the filter? Or has someone an other idea or solution to get this 
> behavior?
>
> Thanks in advance!
>
> Regards,
> Jannik
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group, send email to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to