The Disable button is missing for Multibranch jobs based on a Template after upgrading

This article references an issue that affects a product version that is no longer supported. Please verify the version listed in the article applies to your situation. If unsure, please submit a support ticket at: https://support.cloudbees.com/.

Issue

After upgrading to CloudBees CI version 2.462.3.3, the Disable button is no longer available on job pages for Multibranch Pipeline jobs created from a Pipeline Template Catalog.

Attempting to install the Disable Job Button plugin does not restore the Disable button functionality for Multibranch jobs based on a Template.

Environment

Resolution

This issue is fixed in CloudBees CI 2.504.3.28224 or newer.

Upgrade CloudBees CI to version 2.504.3.28224 or newer to resolve this issue.

Workaround

To disable a Multibranch Pipeline job based on a Template, use the URL method:

Navigate to the job page in your browser.
Append /disable to the end of the job URL:
```
$JENKINS_URL/job/$JOB_NAME/disable
```
Press Enter to load the URL.
Click Retry Using POST when prompted.
The job will be disabled and displayed with a greyed out icon.

To re-enable the job, use the same process with /enable:

$JENKINS_URL/job/$JOB_NAME/enable

This workaround is only needed if you cannot upgrade to version 2.504.3.28224 or newer.

Tested product/plugin versions

CloudBees CI on modern cloud platforms - managed controller - 2.462.3.3

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.