Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
-
Remoting 3.32, jenkins-2.182
Description
It is a follow-up to JENKINS-48766. https://github.com/jenkinsci/jenkins/commit/dbc75125c565905a9c07b0c83d6ae71b2681c67f in Jenkins 2.104+ exposes the "Remoting-Minimum-Version" header.
It would be great if Remoting verifies this header during the connection and refuses to connect if the version is not supported. If the header is missing, the connection should proceed without a warning.
Attachments
Issue Links
- relates to
-
JENKINS-48766 Jenkins Core should provide info about minimum supported Remoting version in API/REST API/logs
-
- Resolved
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue relates to |
Labels | compatibility diagnostics newbie-friendly |
Summary | Jenkins agent should | Remoting should check the |
Summary | Remoting should check the | Remoting should check the "Remoting-Minimum-Version" header when connecting to the master |
Description |
It is a follow-up to It would be great if Remoting verifies this header during the connection and refuses to connect if the version is not supported. |
It is a follow-up to It would be great if Remoting verifies this header during the connection and refuses to connect if the version is not supported. If the header is missing, the connection should proceed without a warning. |
Assignee | Abhishek Gautam [ gautamabhishek46 ] |
Assignee | Abhishek Gautam [ gautamabhishek46 ] | Long Nguyen [ vulong237 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Released As | Remoting 3.32 | |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Fixed but Unreleased [ 10203 ] |
Released As | Remoting 3.32 | Remoting 3.32, jenkins-2.182 |
Status | Fixed but Unreleased [ 10203 ] | Resolved [ 5 ] |
Core side done in 2.171.