Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-48766

Jenkins Core should provide info about minimum supported Remoting version in API/REST API/logs

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: core
    • Labels:
      None
    • Similar Issues:

      Description

      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 Baptiste Mathus)

      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

        Attachments

          Issue Links

            Activity

            oleg_nenashev Oleg Nenashev created issue -
            oleg_nenashev Oleg Nenashev made changes -
            Field Original Value New Value
            Status Open [ 1 ] In Progress [ 3 ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue is related to JENKINS-48761 [ JENKINS-48761 ]
            oleg_nenashev Oleg Nenashev made changes -
            Description 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
            ** 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
            oleg_nenashev Oleg Nenashev made changes -
            Issue Type Bug [ 1 ] New Feature [ 2 ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue is related to JENKINS-48754 [ JENKINS-48754 ]
            oleg_nenashev Oleg Nenashev made changes -
            Remote Link This issue links to "https://github.com/jenkinsci/jenkins/pull/3212 (Web Link)" [ 19709 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Link JENKINS-46154 [ 184393 ]
            oleg_nenashev Oleg Nenashev made changes -
            Description 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
            ** 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
            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
            ** 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
            oleg_nenashev Oleg Nenashev made changes -
            Description 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
            ** 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
            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
            oleg_nenashev Oleg Nenashev made changes -
            Remote Link This issue links to "https://github.com/jenkinsci/jenkins/pull/3250 (Web Link)" [ 19907 ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue relates to JENKINS-50095 [ JENKINS-50095 ]
            oleg_nenashev Oleg Nenashev made changes -
            Status In Progress [ 3 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue relates to JENKINS-50211 [ JENKINS-50211 ]

              People

              • Assignee:
                oleg_nenashev Oleg Nenashev
                Reporter:
                oleg_nenashev Oleg Nenashev
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: