[JENKINS-71027] Files are not copied to agents, scripts are not executed

[jenkins-infra-bot]

The changes that were made in one of the last updates (#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?

---

Originally reported by malice00, imported from: Files are not copied to agents, scripts are not executed

• status: Open
• priority: Major
• component(s): slave-setup-plugin
• resolution: Unresolved
• votes: 0
• watchers: 2
• imported: 20251216-225446

Raw content of original issue

The changes that were made in one of the last updates (#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?

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  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-70622
  
  Alternately, you can switch back to the older version that was working for you and continue using that older version.
  

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-70622">JENKINS-70622

Alternately, you can switch back to the older version that was working for you and continue using that older version.

[jenkins-infra-bot]

malice00:

• Original comment link
• Raw content of original comment:

  markewaite I already forked the repo to see if I could maybe send a PR, but if the plugin is up for adoption, I could look into adopting... Until then, I will definitely revert the plugin to get things running smoothly again.
  Thanks for the heads up.
  

markewaite I already forked the repo to see if I could maybe send a PR, but if the plugin is up for adoption, I could look into adopting... Until then, I will definitely revert the plugin to get things running smoothly again.
Thanks for the heads up.