[JIRA] (JENKINS-58095) Add support for configurable "Restrict jobs execution at node" and "Environment variables" equivalent of generic nodes

[michelzan...@gmail.com (JIRA)]

Title: Message Title

Michel Zanini commented on JENKINS-58095   Re: Add support for configurable "Restrict jobs execution at node" and "Environment variables" equivalent of generic nodes Hi Basil Crow, Can you take a look at jenkinsci/swarm-plugin#80 and see if this doesn't address your use case here? That adds support to Environment variables and works ok, but it has not being officially made part of a release yet. It's not released. It would be useful to release the master branch now to include it. When you say "supported" in the past tense, do you mean that you had job name regular _expression_ filtering working already with a static (non-Swarm) agent? I am trying to determine if this problem is unique to Swarm or would apply to any Jenkins agent. I believe what he meant here is that he uses https://wiki.jenkins.io/display/JENKINS/Job+Restrictions+Plugin, which implements a regex filter on job names. I also use this plugin and filter. The issue here is that Swarm can't support this as the Node Property gets re-created if the slave disconnects and connects again. It's basically the same issue as with env variables and tool locations, but now in a Node Property coming from a custom plugin. I had a look at the code and could not come up with a way we could add support for a Node Property provided by a plugin. The only way I could think would be to dynamically check on server part of the plugin if a certain plugin is installed and add the Node Properties... but the client side has to have a way of sending a big payload configuring the Node Property. For example, Job Restriction plugin contain a list of filters, and the filters need configuration as well such as the regex string. This all has to be sent from the client side and constructed on the server side. Seems hard, but do you have any ideas how to support Job Restrictions Plugin with Swarm? Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200137.1560953853000.6298.1576151160161%40Atlassian.JIRA.