-
Suggestion
-
Resolution: Done
-
None
-
JDK 1.6.0_29, CentOS 5.8, MySQL 5.5
Recently we found our Bamboo server disk space hitting particular free space thresholds. We configured stricter artifact retention policies for some of our more artifact-heavy plans, and increased base restrictions for the global expiry.
While we can see the build expiry process running, it seems to taking more than a week to get through a full build expiry run, even though we've set Bamboo to run build expiry every night.
The expiry process needs to be more performant. It seems to be a serial process, so multi-threading it would be a start.
Additionally, instead of an expiry process kicking off at the global expiry time, it might be a possibility to have each build run the plan expiry process at the end of the build.
- copied to
-
BDEV-1054 Failed to load
[BAM-11711] Improve performance of build expiry process
Remote Link | Original: This issue links to "BDEV-1054 (EACJ)" [ 21742 ] | New: This issue links to "BDEV-1054 (Hello Jira)" [ 21742 ] |
Workflow | Original: JAC Suggestion Workflow [ 3015912 ] | New: JAC Suggestion Workflow 3 [ 3602119 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2701265 ] | New: JAC Suggestion Workflow [ 3015912 ] |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1420106 ] | New: Confluence Workflow - Public Facing v4 [ 2701265 ] |
Resolution | Original: Fixed [ 1 ] | New: Done [ 17 ] |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 609234 ] | New: Bamboo Workflow 2016 v1 [ 1420106 ] |
Workflow | Original: Bamboo Workflow 2014 [ 600643 ] | New: Bamboo Workflow 2014 v2 [ 609234 ] |
Workflow | Original: Bamboo Workflow 2010 [ 390388 ] | New: Bamboo Workflow 2014 [ 600643 ] |