Hi Vladimir,

thank you very much for your detailed explanation. I just set up my Jenkins 
according to your screenshots.
The problem I am having is, that the Node label parameter factory (when 
given something like docker&&platformA) seems to not be able to recognize 
the node labels of unstarted Docker images.
I would like to have the needed images to be automatically started (and 
stopped once they are finished). I think unstarted images do not even have 
a real Nodename that can be passed as a parameter.

Do you use this setup with Docker or other clouds?

Thanks,
Julianus

Am Dienstag, 19. Januar 2016 18:17:59 UTC+1 schrieb zakyn:
>
>
> Hello,
>
> I just set it without any problem.
>
> You need one job which will trigger the job(s) on all slaves on all nodes 
> with given label(s).
>
> 3rdparty_all job triggeres 3rdparty job on all nodes which fit "3rdparty" 
> labels.
>
> See attachments. I hope it is clear.
>
> Best regards,
>
> Vladimir
>
>
>
>
>
>
> ------------------------------
> Date: Tue, 19 Jan 2016 08:13:43 -0800
> From: [email protected] <javascript:>
> To: [email protected] <javascript:>
> Subject: Run job on ALL cloud (i.e. Docker) slaves including a given label
>
> Hello everybody,
>
> currently I am desperately looking for a way to create a Jenkins job that, 
> when launched, will be executed concurrently
> on ALL slaves matching a label (or better a set of labels).
> Usually (but not exclusively) my slaves will be cloud based. That means 
> they should be fired up automatically with the Docker plugin of Jenkins.
>
> I tried some different configurations (e.g. Elastic Axis Plugin, Matrix 
> plugin [and its label_expressions], Restricting job to certain slaves in 
> its configuration) but either it does not work at all or Jenkins will only 
> fire up the job on one slave (that matches the label) only.
>
> The method I am looking for should work on labels because I do not want to 
> click all the slaves that should be used for a certain job everytime my 
> configuration changes (i.e. via a slaves axis).
> Has anyone found a way of doing what I envision?
>
> Your help is highly appreciated.
> Regards,
> Julianus
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/9dfd9ba5-052b-4f23-9a05-fe2ab3ce17c7%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/9dfd9ba5-052b-4f23-9a05-fe2ab3ce17c7%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2650806c-1d4e-47ca-97c5-16b9eec2be59%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to