-
Bug
-
Resolution: Unresolved
-
Major
-
None
The changes that were made in one of the last updates (https://github.com/jenkinsci/slave-setup-plugin/pull/11) have broken our setup:
We have a job that cleans all out agents and then restarts them. Before the updates that started caching if data has been copied and scripts executed, this would reinitialize our agents. Now, because the plugin assumes the agent is already setup, no data is copied and no initialization is done.
I understand that in some cases this caching is nice to have, but for our use-case, we would like to have the old behavior back. Maybe it is possible to configure whether or not to use caching?
malice00 I'm sorry that the latest update to the plugin is causing you trouble. Unfortunately, I don't plan to spend more time on the plugin. I don't use the plugin and don't have the capacity to maintain it further. I am sorry that a five year old pull request that was finally released has caused you trouble. That is most unfortunate.
The plugin is up for adoption. I invite you to adopt the plugin, modernize it, implement the feature that you're seeking, and release a new version. You can read more about history of the plugin in
JENKINS-70622Alternately, you can switch back to the older version that was working for you and continue using that older version.