[JIRA] [lockable-resources-plugin] (JENKINS-30056) Reserving lockable resources for nodes

[mihai_darius22@yahoo.com (JIRA)]

Darius Mihai created an issue

Jenkins / JENKINS-30056 Reserving lockable resources for nodes Issue Type: New Feature Assignee: Unassigned Components: lockable-resources-plugin Created: 20/Aug/15 1:34 PM Priority: Minor Reporter: Darius Mihai A mechanism that allows resources to only be used by certain nodes (slaves) in the network for finer control over where a build can run. Moreover, having such functionality might be used to limit the number of executions of a build on those machines (having N resources that can be used by a slave will also limit the number of instances that can run on that slave to N, at most). This functionality is implemented in pull request 15. See https://github.com/jenkinsci/lockable-resources-plugin/pull/15 for changes. Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[michal.fuchs@nxp.com (JIRA)]

Michal Fuchs commented on JENKINS-30056

Re: Reserving lockable resources for nodes This is exactly what I am looking for. What is needed to push it forward?

Add Comment

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

[cuanu@gmx.de (JIRA)]

Felix Kolk commented on JENKINS-30056

Re: Reserving lockable resources for nodes

Hey, is there anybody who could use this feature? Does anybody have a workaround for the meantime?

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[tobias-jenkins@23.gs (JIRA)]

Tobias Gruetzmacher closed an issue as Won't Do

As said in my closing comment on the linked pull requests:   I consider this feature out-of-scope for this plugin. If someone wants to revive this effort, I would propose creating an extension point for "dynamic labels" and adding this feature using a new plugin extending this one.

Jenkins / JENKINS-30056

Reserving lockable resources for nodes

Change By: Tobias Gruetzmacher Status: Open Closed Resolution: Won't Do

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)