Thanks Mark :)
1. Yes. I was referring to old slave.jar
2. I now understand it is not related at all to my upgrade but more to me
coupling the upgrade and installing version column plugin together.
3. I completely agree those 2 tickets should resolve the issue.
Thanks.
Tzach
On Fri, Feb 9, 2024
On Thursday, February 8, 2024 at 11:47:29 PM UTC-7 dheinric wrote:
Am Donnerstag, dem 08.02.2024 um 08:20 -0800 schrieb tzach solomon:
"This node is offline because it uses an old"
Old what?
An old agent.jar (or the deprecated term for agent, in the case of the
older plugin version used
Am Donnerstag, dem 08.02.2024 um 08:20 -0800 schrieb tzach solomon:
"This node is offline because it uses an old"
Old what?
Bye...
Dirk
--
Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email:
OK. so my problem was that i did not use the exact build same as the
built-in node, meaning, in Jenkins 2.332.3 the built-in version is 4.13 and
i've used 4.13.3, thus it showed me "This node is offline because it uses
an old" which is misleading..
Tzach
On Thu, Feb 8, 2024 at 6:20 PM tzach
Hi,
I've updated our Jenkins from 2.332.2 to 2.332.3 and now I'm starting to
get "This node is offline because it uses an old" messages in our nodes.
How can I know what is the minimum version that my Jenkins needs in order
to supply the requirement?
Thanks,
Tzach
--
You received this
