[JIRA] (JENKINS-61807) "restrict where this project can be run" setting missing from job configuration
Title: Message Title Stephen Smith closed an issue as Fixed Jenkins / JENKINS-61807 "restrict where this project can be run" setting missing from job configuration Change By: Stephen Smith Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205652.1585948729000.7892.1586300640283%40Atlassian.JIRA.
[JIRA] (JENKINS-61807) "restrict where this project can be run" setting missing from job configuration
Title: Message Title Stephen Smith commented on JENKINS-61807 Re: "restrict where this project can be run" setting missing from job configuration Thank you, this is the route I ended up taking, and it works like a charm. This ended up being a problem of not being able to resolve old documentation from new functionality. I'll close the issue. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205652.1585948729000.7890.1586300580110%40Atlassian.JIRA.
[JIRA] (JENKINS-61807) "restrict where this project can be run" setting missing from job configuration
Title: Message Title Stephen Smith updated an issue Jenkins / JENKINS-61807 "restrict where this project can be run" setting missing from job configuration Change By: Stephen Smith Environment: Jenkins version: 2.222.1OS: Windows Server 2016Browser: Google Chrome Version 80.0.3987.149 Plugs Plugins : a large list, not sure which are relevant Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205652.1585948729000.6319.1585948800239%40Atlassian.JIRA.
[JIRA] (JENKINS-61807) "restrict where this project can be run" setting missing from job configuration
Title: Message Title Stephen Smith created an issue Jenkins / JENKINS-61807 "restrict where this project can be run" setting missing from job configuration Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-04-03 21:18 Environment: Jenkins version: 2.222.1 OS: Windows Server 2016 Browser: Google Chrome Version 80.0.3987.149 Plugs: a large list, not sure which are relevant Labels: jenkins slave configuration windows Priority: Blocker Reporter: Stephen Smith I have a master node, and I just added a slave node running as a service. A single machine runs jenkins, the master node, and the slave node. Both master and slave nodes have labels, and they are both connected and running. However, in attempting to set up a project to build on this slave node as per https://scmquest.com/jenkins-master-slave-setup-and-configuration-with-screenshots/ the "Restrict where this project can be run" option is missing from the "general" section. On a single branch project, I see the options "Discard old builds," "Do not allow concurrent builds ," and "Do not allow the pipeline to resume if the master restarts." But not the actual option i need: "Restrict where this project can be run." In a multibranch project, I don't see any additional options at all. I'm at a loss of how to proceed from here. I can try using another plugin to restrict which nodes build which project as a workaround to this broken feature, but it would be nice if the feature just worked. Is there further troubleshooting I can perform at my end?
