-
Bug
-
Resolution: Fixed
-
Major
-
-
Remoting 3.33, jenkins-2.182
This change https://github.com/jenkinsci/remoting/pull/193/commits/69f9ebe72c608e14745fb3fc5f8d9e4c65758d89 is modifying the behaviour of the agent connection cycle.
Retrying the connection even when the agent is not yet created in the master was something a cloud implementation could rely on (one of our proprietary implementations does).
IMHO this was a breaking change. There should be at least one way to keep the previous behaviour (with a new parameter, or maybe reusing the existent "noReconnect").
- is caused by
-
JENKINS-46515 Launcher will retry connections forever under some irrecoverable status
-
- Closed
-
- relates to
-
JENKINS-57759 Revert remoting bump to avoid regression
-
- Resolved
-
[JENKINS-57713] Cloud agent provisioning errors due to Remoting behaviour change
Link |
New:
This issue is caused by |
Summary | Original: Remoting changing behaviour | New: Cloud agent provisioning errors due to Remoting behaviour change |
Labels | New: regression |
Link |
New:
This issue relates to |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Released As | New: Remoting 3.33 | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Fixed but Unreleased [ 10203 ] |
Released As | Original: Remoting 3.33 | New: Remoting 3.33, jenkins-2.182 |
Status | Original: Fixed but Unreleased [ 10203 ] | New: Resolved [ 5 ] |