Issue
On the page, selecting the Stay in "quieting down" state when restarted checkbox does not persist.
After selecting the checkbox and navigating away to another page, returning to the Quiet Restart page shows the checkbox as unchecked again.
No error message is displayed in the UI.
On the backend, QuietStartConfiguration.isActivated() returns false after the page reload, confirming the setting was never saved.
This prevents administrators from using Quiet Start to keep a restarted controller in the quieting-down state.
Environment
-
CloudBees CI on modern cloud platforms - operations center ≥ 2.568.1.37445 and < 2.568.3.37907
-
CloudBees CI on modern cloud platforms - managed controller ≥ 2.568.1.37445 and < 2.568.3.37907
-
CloudBees CI on traditional platforms - operations center ≥ 2.568.1.37445 and < 2.568.3.37907
-
CloudBees CI on traditional platforms - client controller ≥ 2.568.1.37445 and < 2.568.3.37907
-
CloudBees Quiet Start plugin ≥ 1.121 and < 1.126
Explanation
The checkbox is wired to a backend call through the plugin’s @JavaScriptMethod binding, QuietStartConfiguration#setActivated().
A change shipped in CloudBees Quiet Start plugin version 1.121 broke this binding.
As a result, selecting the checkbox only updates the browser state, and the backend method that persists the setting is never invoked.
Plugin version 1.111 is not affected.
Resolution
Upgrade to CloudBees CI version 2.568.3.37907 or newer to resolve this issue. This updates CloudBees Quiet Start plugin to version 1.126 or later, which restores the backend call made when the checkbox is selected.
Workaround
If unable to upgrade immediately, use a Groovy init script to put the controller in the quieting-down state on every startup instead of relying on the checkbox:
-
Create a file named
quiet-start.groovyin the$JENKINS_HOME/init.groovy.d/directory. -
Add the following content to the file:
import jenkins.model.Jenkins Jenkins.instance.doQuietDown() -
Restart the controller and confirm it starts in the quieting-down state.
| This workaround must be configured on each affected controller individually, and it remains in place until the file is removed or the plugin is upgraded. |