[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-38516) "Parsing cucumber.json" blocked by parallel job executions

2016-11-09 Thread mid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 noob alot commented on  JENKINS-38516  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Parsing cucumber.json" blocked by parallel job executions   
 

  
 
 
 
 

 
 Forgive my ignorance w Jenkins: What if the updating part was done in a separate thread so the build itself can complete?  
 

  
 
 
 
 

 
 
 

 
 
 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-38516) "Parsing cucumber.json" blocked by parallel job executions

2016-11-09 Thread mid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 noob alot edited a comment on  JENKINS-38516  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Parsing cucumber.json" blocked by parallel job executions   
 

  
 
 
 
 

 
 I'm also affected by this issue.The plugin uses Checkpoints, which wait for the status of previous build . :  Looking at the code, I don't really see why this was done. https://github.com/jenkinsci/cucumber-testresult-plugin/blob/master/src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultArchiver.java#L167 This code was originally added here: https://github.com/jenkinsci/cucumber-testresult-plugin/commit/c4c0274ec9cb6d14a8155d5152823d4c271561ad#diff-49f27251bb42a6e90637f8082b4c7321And was modified support pipeline builds:https://github.com/jenkinsci/cucumber-testresult-plugin/pull/8https://github.com/jenkinsci/cucumber-testresult-plugin/pull/8/files#diff-49f27251bb42a6e90637f8082b4c7321R160 It seems the status/data of the previous build isn't used. I suggest removing the checkpoints.  
 

  
 
 
 
 

 
 
 

 
 
 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-38516) "Parsing cucumber.json" blocked by parallel job executions

2016-11-09 Thread mid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 noob alot commented on  JENKINS-38516  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Parsing cucumber.json" blocked by parallel job executions   
 

  
 
 
 
 

 
 I'm also affected by this issue. The plugin uses Checkpoints, which wait for the status of previous build. Looking at the code, I don't really see why this was done. https://github.com/jenkinsci/cucumber-testresult-plugin/blob/master/src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultArchiver.java#L167 It seems the status/data of the previous build isn't used.  I suggest removing the checkpoints.  
 

  
 
 
 
 

 
 
 

 
 
 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.