[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Jesse Glick commented on JENKINS-61937 Re: hpi:run fails on Java 8 when the plugin depends on 2.230+ Sure. Does it work? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.23930.1588982160144%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Jesse Glick commented on JENKINS-61937 Re: hpi:run fails on Java 8 when the plugin depends on 2.230+ This clearly looks like a case of maven-hpi-plugin being insufficiently robust. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.23832.1588962540198%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-61937 hpi:run fails on Java 8 when the plugin depends on 2.230+ Change By: Jesse Glick Labels: lts-candidate regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.23830.1588962480160%40Atlassian.JIRA.
[JIRA] (JENKINS-55973) Update Jenkins POM and Core to SpotBugs
Title: Message Title Jesse Glick started work on JENKINS-55973 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197384.1549366215000.23676.1588946949761%40Atlassian.JIRA.
[JIRA] (JENKINS-55973) Update Jenkins POM and Core to SpotBugs
Title: Message Title Jesse Glick commented on JENKINS-55973 Re: Update Jenkins POM and Core to SpotBugs What is the overall status here? Core is patched; do we need something done in plugin POMs? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197384.1549366215000.23679.1588946949923%40Atlassian.JIRA.
[JIRA] (JENKINS-62181) Remoting deadlock when launching remote agent
Title: Message Title Jesse Glick updated JENKINS-62181 Jenkins / JENKINS-62181 Remoting deadlock when launching remote agent Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206113.1588790553000.23226.1588863960268%40Atlassian.JIRA.
[JIRA] (JENKINS-62181) Remoting deadlock when launching remote agent
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-62181 Remoting deadlock when launching remote agent Change By: Jesse Glick Labels: deadlock lts-candidate regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206113.1588790553000.23223.1588863660166%40Atlassian.JIRA.
[JIRA] (JENKINS-62181) Remoting deadlock when launching remote agent
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-62181 Remoting deadlock when launching remote agent Change By: Jesse Glick Component/s: core Component/s: remoting Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206113.1588790553000.23214.1588863600894%40Atlassian.JIRA.
[JIRA] (JENKINS-62181) Remoting deadlock when launching remote agent
Title: Message Title Jesse Glick started work on JENKINS-62181 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206113.1588790553000.23221.1588863601389%40Atlassian.JIRA.
[JIRA] (JENKINS-62181) Remoting deadlock when launching remote agent
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-62181 Remoting deadlock when launching remote agent Change By: Jesse Glick Assignee: Jeff Thompson Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206113.1588790553000.23218.1588863601005%40Atlassian.JIRA.
[JIRA] (JENKINS-62181) Remoting deadlock when launching remote agent
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-62181 Remoting deadlock when launching remote agent Change By: Jesse Glick Labels: deadlock regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206113.1588790553000.23209.1588863600713%40Atlassian.JIRA.
[JIRA] (JENKINS-62181) Remoting deadlock when launching remote agent
Title: Message Title Jesse Glick commented on JENKINS-62181 Re: Remoting deadlock when launching remote agent The “new” method was just an override of an existing synchronized method, though the deadlock does smell like a regression in the new code before the super call. You have a custom logger on hudson.remoting.Channel (or hudson.remoting) at FINE or below I think? As a workaround, try removing that logger. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206113.1588790553000.23205.1588863240399%40Atlassian.JIRA.
[JIRA] (JENKINS-49073) build job propagate true propagates FAIL when state is UNSTABLE
Title: Message Title Jesse Glick commented on JENKINS-49073 Re: build job propagate true propagates FAIL when state is UNSTABLE Should this bug be re-opened As a general rule: no, not unless the originally described bug was not in fact fixed. If a change causes some undesirable behavior, file a separate bug with a Link to the original. In this case there is no bug, your script was simply relying on undocumented behavior. The FlowInterruptedException does include all the same information, just in a DownstreamFailureCause rather than the Throwable.message. Anyway using a catch block and the exception here was the wrong idiom even before this change. Set propagate: false and inspect the resulting build object’s status and other fields. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187899.1516619705000.22560.1588765920379%40Atlassian.JIRA.
