Using all agents available

9 views
Skip to first unread message

Hari Kodungallur

unread,
Apr 30, 2013, 1:51:35 PM4/30/13
to jenkins...@googlegroups.com
Hello,

I am a new Jenkins user. I am looking through tools that have a support for the following functionality or similar.

I want to configure a pool of agents that can either do builds or tests. But when a particular type of test comes in, I would like to use all available agents and kick off tests on them. 

Suppose I have 5 agents in the pool. They are just waiting for jobs -- builds or tests. Let us say two of them get busy doing builds. And at this time I kick off my test. It should detect that three of the agents are idle and kick off tests on the three agents. At a later time, possibly all 5 agents are idle and I want the test to be kicked off on all 5 of them. 

I am wondering if there a feature or a plugin in Jenkins that can accomplish this task. 

Thank you much.
-Hari

Scott Evans

unread,
Apr 30, 2013, 2:45:28 PM4/30/13
to jenkins...@googlegroups.com
Just put a label on the agents and assign both the build and test jobs to that label and it should work just as you expect.  Note that unless you use a matrix configuration, a job will only use one agent at a time, so you'd want to look into matrix jobs if you have several sets of tests you want to run against a single job configuration.


-Hari

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Hari Kodungallur

unread,
Apr 30, 2013, 4:16:47 PM4/30/13
to jenkins...@googlegroups.com
Thank you much Scott. 
I don't quite understand it fully -- expected as I don't understand the Jenkins terminology yet. Let me try out whatever you mentioned and I will send updates / follow up questions after that. 

Thanks,
-Hari





--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/OlYAG-zu4dg/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.

Hari Kodungallur

unread,
May 3, 2013, 2:53:27 PM5/3/13
to jenkins...@googlegroups.com
Thanks Scott.

This works only partially. I can get it to build on all slaves that are in the pool. But I would like it to build only on all *available* slaves. That is, if I have [slave1, slave2, slave3] in the pool and if slave1 is currently doing a different build, I want the my build to use slave2 and slave3 only and *not* queue up a job on slave1. 

I am trying to see if the answer given in http://jenkins.361315.n4.nabble.com/Run-a-build-concurrently-on-all-slaves-td4651190.html will work with NodeLabel Parameter plugin, so far unsuccessful trying to pass label parameters across. Also, don't know even if I am able to pass the parameters correctly, it will behave like I want it (as explained above).


Thanks,
-Hari



Reply all
Reply to author
Forward
0 new messages