usually i am interested in the build history and some artifacts. Both are stored in the server workspace. This can be controlled with minimum/maximum settings. However, i am interested more in the build history, rather than the complete build artifacts (of the agent). If i reduce the minimum setting, i will free the agent workspace, that i am no longer interested in. However, this will reduce the number of entries in the build history. Imo the agent should have its own cleanup policy for the workspace.
The agent workspace cleanup policy is, to a certain extent, separate. It runs when every build finishes. If you tick the “all of above” tick box, then the agent workspace will be cleaned up for every build regardless of the server cleanup policy.
As you are not interested in the agent workspace, this appears to fit your requirement?
not sure, if this fits. For debugging purposes we generally have disabled “[ ] fails”. We have set mininum builds to 1 and maximum builds to 2. I noticed, that one build which failed, does not get deleted. Not even after the seven day cleanup build age.
It should clean up, I’ll do some testing tomorrow and see if I can reproduce.
Can you share your full cleanup settings? I think the issue is that the server policy only cleans up the agent workspace, after the whole server workspace is cleaned up. If you only cleanup up one workspace area, e.g. Other Files, then the agent workspace remains.
According to the description on the cleanup page, the server policy should clean up the agent workspace every time it runs regardless on the “what to cleanup” options. We’ll work on making that happen for the next version.
i have just noticed, that one of the 3 configurations, which override the default is configured to cleanup every 14 months. I did not have the chance yet, to ask my teammate, if this is by intention.
Nevertheless, it should be possible to configure the duration for storing build logs and server artifacts independently of the agent workspace. We have some projects, such as the one mentioned in this post, that take up to 8 GB of disk space. We don’t want to store several of those builds entirely, nor do we need them.
Yes, we agree. We would like to have multiple cleanup policies, to allow you to set different maximums and ages for each separate cleanup item. This has been on our to-do list for some time, but it’s not a quick task and requires some thought to ensure that we get it right. I can understand how this is a priority for you, so will spend some time looking into what we would need to to do today.
All I can say is that its being worked on.