[JIRA] (JENKINS-38412) Starvation can occur if job isn't restricted
Title: Message Title Pavel Janoušek resolved as Fixed Merged. Jenkins / JENKINS-38412 Starvation can occur if job isn't restricted Change By: Pavel Janoušek Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38412) Starvation can occur if job isn't restricted
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38412 Re: Starvation can occur if job isn't restricted Code changed in jenkins User: Ing. Pavel Janousek Path: src/main/java/com/redhat/foreman/ForemanSharedNodeCloud.java http://jenkins-ci.org/commit/foreman-node-sharing-plugin/1738418b9d9e75cf897c07b769b9a4efb8bd7443 Log: JENKINS-38412 Fixed waiting run starvation Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38412) Starvation can occur if job isn't restricted
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38412 Re: Starvation can occur if job isn't restricted Code changed in jenkins User: Scott Hebert Path: src/main/java/com/redhat/foreman/ForemanSharedNodeCloud.java http://jenkins-ci.org/commit/foreman-node-sharing-plugin/650612d34c2a815f32ab3666421427428aade9ca Log: Merge pull request #14 from pjanouse/JENKINS-38412 JENKINS-38412 Fixed waiting run starvation Compare: https://github.com/jenkinsci/foreman-node-sharing-plugin/compare/bc170d434133...650612d34c2a Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38412) Starvation can occur if job isn't restricted
Title: Message Title Pavel Janoušek commented on JENKINS-38412 Re: Starvation can occur if job isn't restricted PR sent. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38412) Starvation can occur if job isn't restricted
Title: Message Title Pavel Janoušek started work on JENKINS-38412 Change By: Pavel Janoušek Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38412) Starvation can occur if job isn't restricted
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-38412 Starvation can occur if job isn't restricted Issue Type: Bug Assignee: Pavel Janoušek Components: foreman-node-sharing-plugin Created: 2016/Sep/21 12:21 PM Priority: Minor Reporter: Pavel Janoušek Thanks to JENKINS-38196 we allow to provision a node for Label=null. It is valid use-case, however it doesn't work as supposed. Jenkins isn't able to schedule run in the queue which isn't restricted to any label to the node which has EXCLUSIVE mode set on. Although we will not use EXCLUSIVE mode if label isn't specified (JENKINS-38366), is isn't sufficient. The real (starvation) scenario: run without restriction appended to the queue canProvision() returns true if it has at least one available node master asks for provision that node from Foreman, node has set labels and instances as EXCLUSIVE master is unable to put the item above to it Although there can be couple of nodes defined in the Foreman instance, situation above can repeat forever and such a job can starve in the queue indefinitely. So if Label=null we should provision only node without any label defined/associated and with non-exclusive mode.
