Resolved Issues
- S3 cache cleanup causing memory spike
-
Fixed an issue where cache cleanup was not correctly clearing the cache and leading to excessive memory use and deletion of customer artifacts and stashes.
Known Issues
- Duplicate plugins in the Operations center Plugin Manager UI
-
When you search for a specific plugin under the Available tab in the Operations center Plugin Manager, the search results show duplicate entries for the plugin.
- High memory usage and unintended artifact deletion due to incorrect S3 prefix in CloudBees Cache Step Plugin (
cloudbees-cache-step) -
In the CloudBees Cache Step Plugin (
cloudbees-cache-step), if you configured workspace caching to use AWS S3, the plugin’s automated cleanup process would delete customer artifacts from the S3 bucket, even when you do not actively use workspace caching in any features.
CloudBees advises disabling cache steps by selecting None (disable caching) from the Cache Manager field of the Workspace Caching section of the System configuration page. This action turns off workspace caching and prevents the cache cleanup process from deleting content in the S3 bucket.