[JIRA] (JENKINS-46515) Launcher will retry connections forever under some irrecoverable status

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated JENKINS-46515

Jenkins / JENKINS-46515 Launcher will retry connections forever under some irrecoverable status Change By: Oleg Nenashev Status: In Progress Review Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[jthompson@cloudbees.com (JIRA)]

Jeff Thompson updated JENKINS-46515

Jenkins / JENKINS-46515 Launcher will retry connections forever under some irrecoverable status

Change By: Jeff Thompson Status: In Review Closed Resolution: Fixed Released As: Remoting 3.30

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated an issue

Jenkins / JENKINS-46515 Launcher will retry connections forever under some irrecoverable status

Change By: Oleg Nenashev Released As: Remoting 3.30 , Jenkins 2.176

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated an issue

Jenkins / JENKINS-46515 Launcher will retry connections forever under some irrecoverable status

Change By: Oleg Nenashev Labels: lts-candidate

Add Comment

[ogondza@gmail.com (JIRA)]

Oliver Gondža updated an issue

Jenkins / JENKINS-46515 Launcher will retry connections forever under some irrecoverable status

Change By: Oliver Gondža Labels: lts-candidate

Add Comment

[jnord@cloudbees.com (JIRA)]

James Nord commented on JENKINS-46515

Re: Launcher will retry connections forever under some irrecoverable status noting that this introduced a regression, where an agent is spun and connects before jenkins has enabled a temporary jnlp endpoint for a cloud.

Add Comment

[jthompson@cloudbees.com (JIRA)]

Jeff Thompson commented on JENKINS-46515

Re: Launcher will retry connections forever under some irrecoverable status

The Remoting release (3.30) containing this change was reverted from Jenkins core because it introduced a regression in some other scenarios, particularly involving cloud agents. I'm going to revert it from the Remoting master branch and create a new release without it and containing the changes included in 3.30. See #JENKINS-57759 and #JENKINS-57713  Javier Delgado (or someone else), if you are interested you can re-open this issue or create a similar one and propose a new approach that resolves the issues described here and maintains sequence needed by the other scenarios.

Add Comment