Add machine policy - package cache retention policy details #2736
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
octopus-hideaki
approved these changes
Jun 4, 2025
| To configure quantity to keep, create a custom [Machine Policy](/docs/infrastructure/deployment-targets/machine-policies) and set the `Package Cache` policy to `Keep a limited number`. This will allow you to specify a number of versions to keep per package in the cache. By default this number of versions will be kept for all packages in the cache. | ||
| To restrict the number of packages to keep, select `From the most recently used packages`, and enter your preferred number of packages to keep. Octopus will ensure that only the least recently used packages and versions are removed. | ||
|
|
||
| Targets configured with this policy use the quantity to keep policy for retention. |
There was a problem hiding this comment.
Targets configured with this policy use the quantity to keep policy for retention.
This line might not be relevant anymore since we simplified the explanation
| @@ -50,8 +50,17 @@ Note that if you use the [Custom Installation Directory](/docs/projects/steps/co | |||
|
|
|||
| #### Packages | |||
|
|
|||
| Packages that are transferred during the deployment are managed based on free disk space. For each deployment, prior to acquiring the package, the free disk space is checked and if less than 20% it will delete the “least used” package(s) from the Tentacle file store location. Packages that gets removed will be reacquired if needed for another deployment. | |||
There was a problem hiding this comment.
What do you think about keeping the callout but only specifying that configurable package cache retention will be rolling out to Octopus Cloud customers first, and then available to Octopus Server customers in Q4 2025?
adrianparker
pushed a commit
to adrianparker/octopus-docs
that referenced
this pull request
Aug 4, 2025
…eploy#2736) * Add machine policy - package cache retention policy details * Remove toggle * Remove extra header * Add feature availability note
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[SC-111979]
Relates to: OctopusDeploy/Issues#9421