[JIRA] (JENKINS-41182) Nodes disappear if "# of executors" is set to 0

2018-02-22 Thread ks.nenash...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kseniia Nenasheva updated  JENKINS-41182  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in PR #3141 and PR #3292  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41182  
 
 
  Nodes disappear if "# of executors" is set to 0   
 

  
 
 
 
 

 
Change By: 
 Kseniia Nenasheva  
 
 
Status: 
 In Review Resolved  
 
 
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-41182) Nodes disappear if "# of executors" is set to 0

2018-02-21 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum edited a comment on  JENKINS-41182  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Nodes disappear if "# of executors" is set to 0   
 

  
 
 
 
 

 
 After JENKINS-47793 ([PR 3141|https://github.com/jenkinsci/jenkins/pull/3141]), and the followup fix in [PR 3292|https://github.com/jenkinsci/jenkins/pull/3292], nodes are no longer able to be configured to have 0 executors, so I think this can be closed as resolved.The second PR was merged into 2.108 as [5c8cc45|https://github.com/jenkinsci/jenkins/commit/5c8cc45]. Screenshot Here is a screenshot of the error I get when attempting to configure a node with 0 executors :     !Screen Shot 2018-02-20 at 11.15.35.png|thumbnail!   
 

  
 
 
 
 

 
 
 

 
 
 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-41182) Nodes disappear if "# of executors" is set to 0

2018-02-20 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-41182  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Nodes disappear if "# of executors" is set to 0   
 

  
 
 
 
 

 
 After JENKINS-47793 (PR 3141), and the followup fix in PR 3292, nodes are no longer able to be configured to have 0 executors, so I think this can be closed as resolved. The second PR was merged into 2.108 as 5c8cc45. Screenshot:
 

  
 
 
 
 

 
 
 

 
 
 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-41182) Nodes disappear if "# of executors" is set to 0

2018-02-20 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41182  
 
 
  Nodes disappear if "# of executors" is set to 0   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Attachment: 
 Screen Shot 2018-02-20 at 11.15.35.png  
 

  
 
 
 
 

 
 
 

 
 
 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-41182) Nodes disappear if "# of executors" is set to 0

2017-02-17 Thread matschinera...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alec Matschiner commented on  JENKINS-41182  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Nodes disappear if "# of executors" is set to 0   
 

  
 
 
 
 

 
 When I had set the node executor to 0 I observed all of the same issues described in the description here. I then tried to just create a new node with the same name, that didn't work since its still in the file system. As noob alot (nice name) mentioned you can edit the config and change the # of executors. I also noticed deleting that node's directory, restarting Jenkins, and then I'm able to create a new node with that name but then you'll have to reconfigure it. I'd like to suggest maybe adding more of a warning when when someone is trying to change the executors to 0 in the node config page.  
 

  
 
 
 
 

 
 
 

 
 
 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-41182) Nodes disappear if "# of executors" is set to 0

2017-02-01 Thread mid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 noob alot edited a comment on  JENKINS-41182  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Nodes disappear if "# of executors" is set to 0   
 

  
 
 
 
 

 
 I see this issue too.I set the executors to 0 by going to the node's config page, changing the executor number, and saving.Then the node disappears. The way I got the node back was to edit the node's config in JENKINS_HOME/nodes/NODE_NAME/config.xml, changing the executors count, and restarting my Jenkins instance. Then the node reappeared.  
 

  
 
 
 
 

 
 
 

 
 
 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-41182) Nodes disappear if "# of executors" is set to 0

2017-02-01 Thread mid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 noob alot commented on  JENKINS-41182  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Nodes disappear if "# of executors" is set to 0   
 

  
 
 
 
 

 
 I see this issue too. I set the executors to 0 by going to the node's config page, changing the executor number, and saving. Then the node disappears.  
 

  
 
 
 
 

 
 
 

 
 
 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-41182) Nodes disappear if "# of executors" is set to 0

2017-01-22 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-41182  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Nodes disappear if "# of executors" is set to 0   
 

  
 
 
 
 

 
 How are you setting nodes count to 0?  
 

  
 
 
 
 

 
 
 

 
 
 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-41182) Nodes disappear if "# of executors" is set to 0

2017-01-18 Thread p...@osuosl.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pono Takamori updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41182  
 
 
  Nodes disappear if "# of executors" is set to 0   
 

  
 
 
 
 

 
Change By: 
 Pono Takamori  
 
 
Summary: 
 Nodes disappear  is  if  "# of executors" is set to 0  
 

  
 
 
 
 

 
 
 

 
 
 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-41182) Nodes disappear is "# of executors" is set to 0

2017-01-18 Thread p...@osuosl.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pono Takamori created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41182  
 
 
  Nodes disappear is "# of executors" is set to 0   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Andrew Bayer  
 
 
Components: 
 core  
 
 
Created: 
 2017/Jan/18 8:59 PM  
 
 
Environment: 
 Jenkins 2.7.2  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Pono Takamori  
 

  
 
 
 
 

 
 When "# of executors" is set to 0 for a node, not only does the node disappear from the listing (as Andrew Bayer pointed out to me), but the node will 404 on it's /computer/$node page. The work around is either to edit the config.xml and restart jenkins or use the script feature. The linked gist contains a script to set the number of executors to 2 which was used a temporary fix in our case. [0] - https://gist.github.com/pono/8ab92fddb9461cd62e45923b910ce81f  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment