Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
How to purge unnecessary release package information
-
We have a set of releases that we re-use on a scheduled basis (several times per day). These releases are never marked as deployed, we just create a new package and release it (thus automatically rejecting the prior package). We don't need to keep the entire history for such releases, and I suspect it is bloating the BuildMaster database. Is there a way to purge the rejected package information for this type of release?
Product: BuildMaster
Version: 5.8.3 -
Have you tried using Retention Policies
to purge rejected release packages?Based on your description I think that will do what you need.
-
That sounds just right. Thanks.
Related question: do the Purge Item Types have any overlap? For example, if I purge a release, does it also purge the associated release packages, execution logs and artifacts?
-
It does purge the packages and logs, but the artifact files themselves are only purged by a Purge Artifacts policy.
This behavior is a little confusing I think - we may change it for v6 (by adding an option).
For now you can work around it by adding a purge artifacts policy too, and either creating it before the other policies (they are run in the order they are first created), or checking the option to "purge orphaned artifacts," since an artifact file would become orphaned if its associated release package has been purged from the database.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login