Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make the Cache directory configurable #5071

droyad opened this issue Nov 8, 2018 · 2 comments


Copy link

commented Nov 8, 2018

The directory for the package cache and tool extraction should be configurable so that it can be moved to a location with more space and/or is faster.

The configure --cacheDirectory C:\octopus\Cache command changes the location of the cache folder. By default it is under <OctopusHome>\<Application> where <Application> is OctopusServer or Tentacle.

This setting affects the location of the BundledPackageStoreCache, PackageCache and Tools folders. All these folders contain data that is derived from other sources and can be cleared when the Octopus Server is not running.

Clearing the folders however does affect deployment speed as those files may need to be re-acquired and extracted (eg deployment tools such as Calamari or AWS CLI), or a package downloaded again from an external feed.

@droyad droyad self-assigned this Nov 8, 2018
@droyad droyad closed this Nov 12, 2018
@octoreleasebot octoreleasebot added this to the 2018.9.7 milestone Nov 12, 2018

This comment has been minimized.

Copy link

commented Nov 12, 2018

Release Note: The package cache and working directory can now be configured


This comment has been minimized.

Copy link

commented Feb 10, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Feb 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
2 participants
You can’t perform that action at this time.