[JENKINS-72688] "This node is offline because it uses an old agent.jar" error is misleading

[jenkins-infra-bot]

Hi,

The text "This node is offline because it uses an old" is misleading since the actual code is looking for the exact match, thus, the error should be "This node is offline because version needed is ". of course should be version we compared to, usually the built-in version

 

Jenkins version: 2.332.3

versioncolumn-plugin: 2.2

---

Originally reported by tzach_solomon, imported from: "This node is offline because it uses an old agent.jar" error is misleading

• status: Open
• priority: Critical
• component(s): versioncolumn-plugin
• resolution: Unresolved
• votes: 0
• watchers: 2
• imported: 20251210-221934

Raw content of original issue

Hi,

The text "This node is offline because it uses an old" is misleading since the actual code is looking for the exact match, thus, the error should be "This node is offline because version needed is <VERSION>". <VERSION> of course should be version we compared to, usually the built-in version

 

Jenkins version: 2.332.3

versioncolumn-plugin: 2.2

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  To be sure that I understand the request, I think that you are saying that the existing message that says "Making <agent> offline temporarily due to the use of an old agent.jar" should instead say something like "Making <agent> offline temporarily due to the use of an agent.jar version <version> instead of the expected version <version>".
  
  If so, then I think this would be better solved by JENKINS-63607 which proposes to accept newer versions of Jenkins remoting without a message.
  

To be sure that I understand the request, I think that you are saying that the existing message that says "Making offline temporarily due to the use of an old agent.jar" should instead say something like "Making offline temporarily due to the use of an agent.jar version instead of the expected version ".

If so, then I think this would be better solved by JENKINS-63607">JENKINS-63607 which proposes to accept newer versions of Jenkins remoting without a message.

[jenkins-infra-bot]

tzach_solomon:

• Original comment link
• Raw content of original comment:

  markewaite thanks for the quick response!
  
  	
  Yes, the more generic solution should be in JENKINS-63607
  	
  In the short term I think its a quick win to change the text, if you could do it would be great, If not, i'll to submit a PR ASAP
  
  
  

markewaite thanks for the quick response!

1. Yes, the more generic solution should be in JENKINS-63607">JENKINS-63607
2. In the short term I think its a quick win to change the text, if you could do it would be great, If not, i'll to submit a PR ASAP

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  You're welcome to submit the text change.
  

You're welcome to submit the text change.

[jenkins-infra-bot]

[Original relates_to from Jira: JENKINS-63607]