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!
Question on Retention Policies
-
I want to clean-up builds within a Release but it is cumbersome to manually reject packages as we have a lot of separate applications being built.
Is there a way to configure the Retention Policy so that it can do the following:1- keep only the last n builds without having to mark them Rejected beforehand
2- keep any previously released versions data.For example, I have releases 1 - 5.0 that have shipped, and 6.0 that is now underway. I want to keep the 1 - 5 released data but while 6.0 is underway only keep the last 20 builds of it.
Product: BuildMaster
Version: 5.8.3 -
There is not; retention policies are primarily there to save disk space in the long term. Is there a way you can write a sort of script to automatically reject the builds you don't want? That might be the best solution, since you can then automatically clean them up.
-
That's what I was afraid of. Thanks.
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