[JIRA] (JENKINS-42043) A NPE in SlaveComputer.setNode shouldn't prevent Jenkins from starting
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-42043 A NPE in SlaveComputer.setNode shouldn't prevent Jenkins from starting Change By: Oleg Nenashev Issue Type: Improvement Bug 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-42043) A NPE in SlaveComputer.setNode shouldn't prevent Jenkins from starting
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-42043 A NPE in SlaveComputer.setNode shouldn't prevent Jenkins from starting Change By: Oleg Nenashev Labels: newbie-friendly robustness 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-42043) A NPE in SlaveComputer.setNode shouldn't prevent Jenkins from starting
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-42043 A NPE in SlaveComputer.setNode shouldn't prevent Jenkins from starting Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-42043) A NPE in SlaveComputer.setNode shouldn't prevent Jenkins from starting
Title: Message Title Andrew Bayer commented on JENKINS-42043 Re: A NPE in SlaveComputer.setNode shouldn't prevent Jenkins from starting That sounds right to me. 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-42043) A NPE in SlaveComputer.setNode shouldn't prevent Jenkins from starting
Title: Message Title Steven Christou commented on JENKINS-42043 Re: A NPE in SlaveComputer.setNode shouldn't prevent Jenkins from starting My $0.02 - I think it should keep the node and act as if it is a disconnected node instead of removing the node (i.e. ignore it and move on with the startup). We should never be removing nodes from the list that fail to connect. We should only remove them if the node is manually removed by an administrator, or the node is removed by the plugin via a timeout. 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-42043) A NPE in SlaveComputer.setNode shouldn't prevent Jenkins from starting
Title: Message Title rsandell commented on JENKINS-42043 Re: A NPE in SlaveComputer.setNode shouldn't prevent Jenkins from starting But what should happen if the operation fails? The stacktrace shows that Jenkins is currently updating all "computers" to see which ones to reuse/what executors to remove. If the node failed to update should it then be considered for reuse or for removal? The error in ec2 plugin suggests that it was a "harmless" mistake and we should probably keep it around, while I would guess in most cases since it is in error it should be removed from the list. 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-42043) A NPE in SlaveComputer.setNode shouldn't prevent Jenkins from starting
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-42043 A NPE in SlaveComputer.setNode shouldn't prevent Jenkins from starting Issue Type: Improvement Assignee: Unassigned Components: core Created: 2017/Feb/14 11:05 PM Labels: robustness Priority: Minor Reporter: Baptiste Mathus Currently, an exception thrown in SlaveComputer.setNode() prevents Jenkins from starting (JENKINS-38389). It would be nice to catch RuntimeException there for robustness, as advised by Jesse Glick there. Add Comment
