RE: Run job on ALL cloud (i.e. Docker) slaves including a given label

2016-01-20 Thread Vladimir Zak 
Hi,
I set it to our local cloud service a year ago. I would start the images in one 
job and then I use the "3rdparty_all" job to run the things there.
But with Docker I am not much familiar because we are "windows company".
I hope this could help.
Best regards,
Vladimir




Date: Wed, 20 Jan 2016 00:42:06 -0800
From: jule...@googlemail.com
To: jenkinsci-users@googlegroups.com
Subject: Re: Run job on ALL cloud (i.e. Docker) slaves including a given label

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: jul...@googlemail.com
To: jenkins...@googlegroups.com
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 concurrentlyon 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 jenkinsci-use...@googlegroups.com.

To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9dfd9ba5-052b-4f23-9a05-fe2ab3ce17c7%40googlegroups.com.

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 jenkinsci-users+unsubscr...@googlegroups.com.

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.
  

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/DUB122-W2524D5708BEF0BA2E867D0ACC20%40phx.gbl.
For more options, visit https://groups.google.com/d/optout.

Re: Run job on ALL cloud (i.e. Docker) slaves including a given label

2016-01-20 Thread Julianus Pfeuffer 
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: jul...@googlemail.com 
> To: jenkins...@googlegroups.com 
> 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 jenkinsci-use...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/9dfd9ba5-052b-4f23-9a05-fe2ab3ce17c7%40googlegroups.com
>  
> 
> .
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
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.

Re: Run job on ALL cloud (i.e. Docker) slaves including a given label

2016-01-19 Thread Jason Swager 
Take a look at the NodeLabel Parameter plugin 
(https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin). 
 This offers a way to start a job with a parameter that is a label and the 
job can run on all matching slaves.  

On Tuesday, January 19, 2016 at 8:13:43 AM UTC-8, Julianus Pfeuffer wrote:
>
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/941f9ecd-e86d-4a58-83a5-3942f90b6fcb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Run job on ALL cloud (i.e. Docker) slaves including a given label

2016-01-19 Thread Vladimir Zak 







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: jule...@googlemail.com
To: jenkinsci-users@googlegroups.com
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 concurrentlyon 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 jenkinsci-users+unsubscr...@googlegroups.com.

To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9dfd9ba5-052b-4f23-9a05-fe2ab3ce17c7%40googlegroups.com.

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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/DUB122-W3509B004B6BC373FBE90C6ACC10%40phx.gbl.
For more options, visit https://groups.google.com/d/optout.

Re: Run job on ALL cloud (i.e. Docker) slaves including a given label

2016-01-19 Thread Eric Pyle 
I believe the problem is that Jenkins will not run multiple instances of 
a job with identical parameters. There have been posts on this list 
recently of users who solve this problem by adding an extra parameter 
which is unique for each job instance.


Regards,
Eric

On 1/19/2016 11:13 AM, Julianus Pfeuffer wrote:

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 jenkinsci-users+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9dfd9ba5-052b-4f23-9a05-fe2ab3ce17c7%40googlegroups.com 
.

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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/569E6B3B.8010504%40cd-adapco.com.
For more options, visit https://groups.google.com/d/optout.