Known Issues
- S3 cache cleanup causing memory spike
-
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.
- Errors resuming declarative builds from older releases after extra restart
-
If a Declarative Pipeline build was running in version 2.492.2.3 (or earlier) and the controller was then upgraded to this release, the build would resume. However, if the controller was restarted a second time, the build would fail. This issue also impacts most running Declarative Pipelines during HA controllers rolling upgrades to this release. This issue is resolved when upgrading to 2.516.1.28662.
- 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.
- Configuration as Code items failed to load Pipeline Catalog based jobs
-
When Jobs based on a Pipeline Catalog are defined with CasC, the controller fails to load the CasC bundle. This causes the controller startup to fail.
A temporary workaround is to disable CasC or to temporarily not define items with CasC until a fix is available.