[#BAM-1794] Bamboo gives the impression that Build Expiry will run at the end of the build

Bamboo

Bamboo gives the impression that Build Expiry will run at the end of the build

Created: 07/Oct/07 09:41 PM Updated: 30/Jul/08 03:15 AM

Component/s:

Administration (General), User Interface

Affects Version/s:

1.2.3

Fix Version/s:

1.2.4

Time Tracking:

Not Specified

Participants:	Brydie McCoy [Atlassian] and Nick White
Since last comment:	23 weeks, 2 days ago
Number of comments:	1
Internal Priority:	5. Lowest
Internal Work Bucket:	Confirmed
Labels:

Description

« Hide

This is probably just a wording / placement problem. The build expiry at the plan level is configured as a post build action therefore leading to the assumption that it will run post build, rather than some arbitrary time in the evening.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Nick White added a comment - 30/Jul/08 03:15 AM

Is it actually possible to expire builds at a more regular frequency?

We currently have an issue where Clover is generated significant (300MB+) build artifacts which we don't really need to keep beyond a couple of builds. In our current environment we are often generating 10+GB of data every day which is then not be expired in a timely manner before disks are filling up.

A post build expiry would be useful in this instance (and as this issue mentions was what I thought would happen).