RELEASED: Public: October 18, 2023
New features
- New section to configure how the new bundle versions will be managed by the instance (BEE-37680)
-
Now in Manage Jenkins > System there is a section to configure how the new bundle versions are managed and applied in the instance.
This section appears if the Bundle Update Timing is enabled and will configure the automatic reloads, restarts and skips.
- Ability to auto reload and auto restart when a new bundle versions for Configuration as Code is detected (BEE-37681)
-
If the Bundle Update Timing feature is enabled, CasC users can configure the instance to reload the bundle automatically or to restart automatically, so that the new version is applied.
Possible configuration methods:
-
If the automatic reload is configured and the hot reload is possible, the instance automatically reloads this new bundle.
-
If the automatic reload is configured and the hot reload is not possible, if the automatic restart is configured, the instance schedules a safe restart.
-
If the automatic reload is not configured and the automatic restart is, the instance will schedule a safe restart.
-
If neither the automatic reload or restart are configured, then the user applies the new bundle version manually.
These configurations cause the instance to ignore the Skip New Versions configuration.
-
- Ability to skip all new bundle versions for Configuration as Code (BEE-37684)
-
If the Bundle Update Timing feature is enabled, CasC users can configure the instance to skip all newly detected bundle versions. The instance keeps its current bundle and does not update the bundle configuration.
If users configure the automatic restart or automatic reload, it is not possible to skip new bundle versions and the configuration is ignored.
- Ability to reject Configuration as Code bundles with warnings (BEE-37685)
-
If the Bundle Update Timing feature is enabled, CasC users can configure the instance to reject new bundle versions if the validation returns warnings and not errors.