-
New Feature
-
Resolution: Fixed
-
Major
-
None
It is a follow-up to JENKINS-48761. Currently Jenkins Core does not specify a minimal-supported version, so users do not even got warnings when they use old Remoting versions without using a Version Column plugin (CC batmat)
I propose to enhance the behavior:
- Define a minimal supported version within the core
- Where to return the data?
- Make the version available via Jenkins API
- The minimal supported version should be returned in TcpAgentListener's headers so that Agent can process it on its side
- Nice2Have: The minimal supported version should returned in the Jenkins WAR Manifest
- Diagnostics:
- Warning in agent connection log when the version older than the Minimal one is connected. The connection whould not be aborted, user should just know he runs in YOLO mode
- Warning in the log on the Remoting side (separate ticket - TODO)
- Nice2Have: Warning on the agent main page
- Nice2Have: Administrative monitor OR support in Version Column Plugin
- Nice2Have: Warning in the Support Core plugin
- is related to
-
JENKINS-48761 Jenkins Agents do not connect after update from version 2.95 to version 2.99 and jobs fail
-
- Closed
-
-
-
- Resolved
-
- relates to
-
-
- Closed
-
-
JENKINS-50095 Remoting should check the "Remoting-Minimum-Version" header when connecting to the master
-
- Resolved
-
- links to
(1 links to)
[JENKINS-48766] Jenkins Core should provide info about minimum supported Remoting version in API/REST API/logs
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Link |
New:
This issue is related to |
| Description |
New:
It is a follow-up to I propose to enhance the behavior: * Define a minimal supported version within the core * Where to return the data? ** Make the version available via Jenkins API ** The minimal supported version should be returned in TcpAgentListener's headers so that Agent can process it on its side ** The minimal supported version should returned in the Jenkins WAR Manifest * Diagnostics: ** Warning in agent connection log when the version older than the Minimal one is connected. The connection whould not be aborted, user should just know he runs in YOLO mode ** Warning in the log on the Remoting side (separate ticket - TODO) ** Nice2Have: Warning on the agent main page ** Nice2Have: Administrative monitor OR support in Version Column Plugin |
| Issue Type | Original: Bug [ 1 ] | New: New Feature [ 2 ] |
| Link |
New:
This issue is related to |
| Remote Link | New: This issue links to "https://github.com/jenkinsci/jenkins/pull/3212 (Web Link)" [ 19709 ] |
| Epic Link |
New:
|
| Description |
Original:
It is a follow-up to I propose to enhance the behavior: * Define a minimal supported version within the core * Where to return the data? ** Make the version available via Jenkins API ** The minimal supported version should be returned in TcpAgentListener's headers so that Agent can process it on its side ** The minimal supported version should returned in the Jenkins WAR Manifest * Diagnostics: ** Warning in agent connection log when the version older than the Minimal one is connected. The connection whould not be aborted, user should just know he runs in YOLO mode ** Warning in the log on the Remoting side (separate ticket - TODO) ** Nice2Have: Warning on the agent main page ** Nice2Have: Administrative monitor OR support in Version Column Plugin |
New:
It is a follow-up to I propose to enhance the behavior: * Define a minimal supported version within the core * Where to return the data? ** Make the version available via Jenkins API ** The minimal supported version should be returned in TcpAgentListener's headers so that Agent can process it on its side ** The minimal supported version should returned in the Jenkins WAR Manifest * Diagnostics: ** Warning in agent connection log when the version older than the Minimal one is connected. The connection whould not be aborted, user should just know he runs in YOLO mode ** Warning in the log on the Remoting side (separate ticket - TODO) ** Nice2Have: Warning on the agent main page ** Nice2Have: Administrative monitor OR support in Version Column Plugin ** Nice2Have: Warning in the Support Core plugin |
| Description |
Original:
It is a follow-up to I propose to enhance the behavior: * Define a minimal supported version within the core * Where to return the data? ** Make the version available via Jenkins API ** The minimal supported version should be returned in TcpAgentListener's headers so that Agent can process it on its side ** The minimal supported version should returned in the Jenkins WAR Manifest * Diagnostics: ** Warning in agent connection log when the version older than the Minimal one is connected. The connection whould not be aborted, user should just know he runs in YOLO mode ** Warning in the log on the Remoting side (separate ticket - TODO) ** Nice2Have: Warning on the agent main page ** Nice2Have: Administrative monitor OR support in Version Column Plugin ** Nice2Have: Warning in the Support Core plugin |
New:
It is a follow-up to I propose to enhance the behavior: * Define a minimal supported version within the core * Where to return the data? ** Make the version available via Jenkins API ** The minimal supported version should be returned in TcpAgentListener's headers so that Agent can process it on its side ** Nice2Have: The minimal supported version should returned in the Jenkins WAR Manifest * Diagnostics: ** Warning in agent connection log when the version older than the Minimal one is connected. The connection whould not be aborted, user should just know he runs in YOLO mode ** Warning in the log on the Remoting side (separate ticket - TODO) ** Nice2Have: Warning on the agent main page ** Nice2Have: Administrative monitor OR support in Version Column Plugin ** Nice2Have: Warning in the Support Core plugin |
| Remote Link | New: This issue links to "https://github.com/jenkinsci/jenkins/pull/3250 (Web Link)" [ 19907 ] |