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!
Release/Build History
-
How do we limit the amount of history (stored artifacts etc) BuildMaster stores?
Due to the vast levels we currently have, we need to store them on a large network drive but this has a negative effect on build performance.
Please advise.
-
UPDATE: this is now handled through Retention Policies
The rest of this post is irrelevant, but is being kept for historical purposes.
<I>
If you have no need to store artifacts for rejected builds, there is a "Purge Artifacts" trigger that's part of the BuildMasterBeta extension that will delete artifacts from disk on rejected builds.If you add the trigger ("Admin" > "Set-up Triggers to Respond to Events"), the artifacts from rejected builds will get deleted from disk at the time of rejection. The old ones will still need to be deleted manually.</I>
-
I will also add that there is a feature in the pipeline named "Release Archiving", which will allow deployed releases to be archived and delete the artifacts from a release for all but deployed builds. It will also delete the execution logs and messages for non-deployed builds.
This feature (at the moment) is not scheduled for any particular release, but it should be coming in one of the next few minor (3.X) releases.
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