[JIRA] (JENKINS-49507) Jenkins Branch Source Plugin Can't Choose Node/Slave
Title: Message Title Fred Ferguson commented on JENKINS-49507 Re: Jenkins Branch Source Plugin Can't Choose Node/Slave Thanks for that. This worked for us being added to our Jenkinsfiles agent { label 'nomad-slave-template-name' } Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49507) Jenkins Branch Source Plugin Can't Choose Node/Slave
Title: Message Title Fred Ferguson closed an issue as Fixed Jenkins / JENKINS-49507 Jenkins Branch Source Plugin Can't Choose Node/Slave Change By: Fred Ferguson Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49507) Jenkins Branch Source Plugin Can't Choose Node/Slave
Title: Message Title Fred Ferguson created an issue Jenkins / JENKINS-49507 Jenkins Branch Source Plugin Can't Choose Node/Slave Issue Type: New Feature Assignee: Ivo Verberk Components: github-branch-source-plugin, nomad-plugin Created: 2018-02-12 15:12 Priority: Minor Reporter: Fred Ferguson We've discovered a problem involving the use of the github branch source plugin and the nomad cloud plugin. We want to be in a situation where no builds are running on the Jenkins master and all are using nomad slaves. Other job types, say freestyle allow to "Restrict where this project can be run" and we specify the name of our Nomad cloud. However there is no option to do that for our Github Organization. When we start a job and there are no cloud slaves running it will sit waiting for an executor until a different job type runs, which starts up a cloud and then the github job jumps on the slave after the original job. It can't create slaves of its own. We plan to primarily use the github branch source (organization) so this presents us with a significant problem. Add Comment