CloudBees Jenkins Platform 2.222.42.0.1 Revision 6

2 minute read

RELEASED: 2020-11-12

Based on Jenkins LTS2.222.42-cb-1

Fixed release

Critical regression fixes in version 2.249.3.2

Version 2.249.3.2 release fixes some critical regressions found in version 2.249.3.1.

CloudBees CI on modern cloud platforms, CloudBees CI on traditional platforms Installing version 2.249.3.2 is required to avoid these issues.

CloudBees Jenkins Enterprise CloudBees Jenkins Enterprise 1.x customers need to download and install using the 1.11.39 installer, which will bundle the corresponding operations center/managed controller versions.

CloudBees Jenkins Platform CloudBees Jenkins Platform operations center and CloudBees Jenkins Platform client controller (2.x.y.z) must be upgraded to version 2.249.3.2. CloudBees Jenkins Platform operations center and CloudBees Jenkins Platform client controller (2.222.x.0.z) must be upgraded to version 2.222.42.0.1-rev6. CloudBees Jenkins Platform operations center and CloudBees Jenkins Platform client controller (2.190.x.0.z) must be upgraded to version 2.190.33.0.2-rev6.

CloudBees Jenkins Distribution No updates necessary.

Security advisory

Security advisory

Security fixes

For the following fixes to take effect, users MUST manually restart their CloudBees CI instance.

OC items in nested folders did not have their RBAC configuration correctly migrated (CTR-2742)

An update in the November rolling release (2.249.3.1) caused an issue with operations center items in nested folders RBAC configurations. This version corrects this operations center items in nested folders RBAC configurations issue by performing an additional migration of the RBAC configuration for all the OC items in the Jenkins instance, not just the items defined at the top level.

Nested folders did not have their RBAC configuration correctly migrated (CTR-2740)

An update in the November rolling release (2.249.3.1) caused an issue with nested folders RBAC configuration. This version corrects this nested folders RBAC configuration issue by performing an additional migration of the RBAC configuration for all the folders in the Jenkins instance, not just the folders defined at the top level.

RBAC permissions were not applied correctly when RBAC on views is disabled(CTR-2748)

Since the November rolling release (2.249.3.1), it’s not possible to define groups on views, so the expected permissions set should be coming from the view’s parent item. However there was a bug which made the permission set to be the root one (ie. whatever is defined at root level).

This fix is making the view use the permission set coming from the view’s owner. So if the view is inside a folder, then the folder groups and roles are applied. Or if the view is on the root level, the global groups and roles are applied.