Project restriction | Slave level configuration - instead project level

30 views
Skip to first unread message

LnT

unread,
Jul 4, 2017, 9:43:11 AM7/4/17
to Jenkins Users, Lakshmi Narayana Tenka
Hi,

Help is needed w.r.t Jenkins Projects and slave nodes.

My Jenkins ver. 1.580 , setup includes

300+ projects
15  slaves nodes. (each nodes is one Windows VM)

I made two slaved nodes off-line for R&D. Now no job is going to these off-line slave nodes and couple of jobs waiting period is high due to unavailability of enough nodes.

Requirement : Is there any configuration settings can be done @ jenkins slave node - such a way , specific named project can be run on particular slave node only.
I see , Such configuration is available @ project level not slave node level.

Issue is  I can not go and configure in each project - as I have numerous number of projects.

Hope you understand my requirement ?

Could you please help here.

Regards,
LnT

Mark Waite

unread,
Jul 4, 2017, 10:12:39 AM7/4/17
to Jenkins Users, Lakshmi Narayana Tenka
The configuration slicing plugin may allow you to assign labels to many jobs at the same time.

If you have jobs that are blocked due to insufficient number of agents, isn't one solution to get more agents?

Mark Waite

--
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/5a5ef577-6b10-4d89-af00-cc78dc8257ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

LnT

unread,
Jul 5, 2017, 6:07:17 AM7/5/17
to Jenkins Users, lakshminar...@ngahr.com
Thanks Mark.
I have gone through configuration slicing plugin. It supports below components where none supports directly - Label Expression of Restrict where this project can be run

Ant version per project
Block Build when Downstream Building Slicer (bool)
Block Build when Upstream Building Slicer (bool)
Custom Workspace Slicer
Discard Old Builds Slicer - Days to keep artifacts
Discard Old Builds Slicer - Days to keep builds
Discard Old Builds Slicer - Max # of builds to keep
Discard Old Builds Slicer - Max # of builds to keep with artifacts
E-mail Notification
Execute shell slicer
Execute Windows batch command slicer
JDK per project
Job Disabled Build Slicer (bool)
Job Disabled Build Slicer (String)
Logstash Slicer
Maven Goals and Options (Maven project)
Maven Incremental Build
Maven top-level targets
Maven Version
MAVEN_OPTS per Maven project
Parameters
Quiet Period Slicer
SCM Timer Trigger Slicer
Tied Label Slicer
Timer Trigger Slicer


And coming to your question -
Build executer #1 is given for each slave node , as only project needs to be executed in a given instance.


Regards,
LnT
Reply all
Reply to author
Forward
0 new messages