[JENKINS-63607] Improve the version column checks for remoting compatibility

we are using a lot of agents with swarm plugin.

all agents always download the agent, and then connect to the server.

installing versions node monitor 2.1 caused all the nodes to go OFFLINE since the version node plugin reports remoting 4.5 ON CLIENT SIDE as too old...

 

simply put - when a node reports it has remoting version 4.5 and the master has remoting version 4.3 -> the node is taken offline.

---
Originally reported by amidar, imported from: Improve the version column checks for remoting compatibility

• status: Open
  
• priority: Minor
  
• component(s): versioncolumn-plugin
  
• label(s): newbie-friendly
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 3
  
• imported: 20251210-221934
  

Raw content of original issue

we are using a lot of agents with swarm plugin.


all agents always download the agent, and then connect to the server.


installing versions node monitor 2.1 caused all the nodes to go OFFLINE since the version node plugin reports remoting 4.5 ON CLIENT SIDE as too old...


 


simply put - when a node reports it has remoting version 4.5 and the master has remoting version 4.3 -> the node is taken offline.

environment

```
jenkins 2.235.5

versioncolumn plugin 2.1
```

4 attachments

- [node_monitoring.PNG](https://issues.jenkins.io/secure/attachment/61393/node_monitoring.PNG)
> 
- [old_agent.PNG](https://issues.jenkins.io/secure/attachment/61394/old_agent.PNG)
> 
- [remoting_mismatch.PNG](https://issues.jenkins.io/secure/attachment/61396/remoting_mismatch.PNG)
> 
- [screencapture-mark-pc2-markwaite-net-8080-computer-configure-2020-09-11-21_12_42-edit.png](https://issues.jenkins.io/secure/attachment/52584/screencapture-mark-pc2-markwaite-net-8080-computer-configure-2020-09-11-21_12_42-edit.png)
>