How does retention work on workers in a worker pool?

When running scripts on a worker in a pool Octopus helpfully copies over packages from the library. They remain there for future executions, which makes some of my heavier deploys perform very well so I’m a big fan of this feature.

I’m unclear, though, on how retention works in these cases. When are those packages deleted? Does it follow the retention rules defined by the lifecycle like any other tentacle? Or are workers handled differently?

Hi @mharen,

Thanks for getting in touch! The retention policy for workers should still follow the Lifecycle retention rules you have define. I don’t believe we have any separate setting to control retention for workers.

If you are having some trouble here or have any questions at all about this, please don’t hesitate to let me know.

Best regards,