The Docker image for CloudBees Jenkins Distribution has been modified so now some internal folders and users are the same than for the other types of packages.
Specifically, the following changes have been applied:
jenkins. Note that the
uidof the user has not changed
cloudbees-jenkins-distributionuser belongs is now
jenkins. Note that the gid of the group has not changed
JENKINS_HOMEis now located in
cloudbees-referer.txtfile is now stored in
As a result of these changes, volume mounts to get a persistent
JENKINS_HOME now need to point to
/var/cloudbees-jenkins-distribution instead of
/var/jenkins_home as stated in the documentation
Upgraded Jenkins OSS LTS from
Upgraded Artifact Manager on S3 Plugin from
Upgraded CloudBees AWS Credentials Plugin from
Upgraded Amazon Web Services SDK library from
Upgraded Blue Ocean Plugin from
Upgraded Bitbucket Pipeline for Blue Ocean from
Upgraded Common API for Blue Ocean from
Upgraded Config API for Blue Ocean from
Upgraded Dashboard for Blue Ocean from
Upgraded BlueOcean Display URL from
Upgraded Events API for Blue Ocean from
Upgraded Git Pipeline for Blue Ocean from
Upgraded GitHub Pipeline for Blue Ocean from
Upgraded i18n for Blue Ocean from
Upgraded JIRA Integration for Blue Ocean from
Upgraded JWT for Blue Ocean from
Upgraded Personalization for Blue Ocean from
Upgraded Pipeline REST API for Blue Ocean from
Upgraded Blue Ocean Pipeline Editor from
Upgraded Pipeline SCM API for Blue Ocean from
Upgraded REST API for Blue Ocean from
Upgraded REST Implementation for Blue Ocean from
Upgraded Web for Blue Ocean from
Upgraded Branch API Plugin from
2.5.2. This release includes a potentially breaking change to how multi-branch scan triggers are configured. It introduces an extension point for organization folders that enables the customization of the children of the organization folder on every organization folder scan. This extension includes a "Child Scan Triggers" setting which sets the scan triggers for the child multi-branch projects.
Previously, users could write scripts to change this value on child projects. This is no longer allowed. Child projects will always use the value provided by the organization folder "Child Scan Triggers" setting and code that attempts to change the scan trigger on child projects will not work.
Upgraded CloudBees Assurance Plugin from
Upgraded Bitbucket Branch Source Plugin from
Upgraded CloudBees Folders Plugin from
Upgraded Copy Artifact Plugin from
Upgraded Credentials Plugin from
Upgraded Credentials Binding Plugin from
Upgraded Deployer Framework Plugin from
Upgraded Amazon EC2 Plugin from
Upgraded GitHub Branch Source Plugin from
Upgraded Jackson2 API Plugin from
Upgraded UI library for Blue Ocean from
Upgraded JUnit Plugin from
Upgraded Kubernetes Plugin from
Upgraded Maven Plugin from
Upgraded Metrics Plugin from
Upgraded CloudBees Jenkins Enterprise License Entitlement Check from
Upgraded Pipeline Graph Analysis Plugin from
Upgraded Pipeline: Model API from
Upgraded Pipeline: Model Definition from
Upgraded Pipeline: Declarative Extension Points API from
Upgraded Pipeline: Stage Tags Metadata from
Upgraded SCM API Plugin from
Upgraded Script Security Plugin from
Upgraded SSH Credentials Plugin from
Upgraded SSH Slaves Plugin from
Upgraded Structs Plugin from
Upgraded User Activity Monitoring Plugin from
User activity is now aggregated on a monthly rather than weekly basis. Existing weekly activity is migrated based on the month containing the start of the week. The UI now shows a combined total of the number of users who have authenticated to Jenkins and users whose commits have been included in builds, along with a table showing the data on which this number is based. A detailed report can be downloaded that shows the months in which a user was active.
Upgraded Pipeline API Plugin from
Upgraded Pipeline Basic Steps Plugin from
Upgraded Pipeline Groovy Plugin from
Upgraded Pipeline Nodes and Processes Plugin from
Upgraded Pipeline Multibranch Plugin from
Upgraded Pipeline SCM Step Plugin from
Upgraded Pipeline: Step API from
Upgraded Pipeline Supporting APIs Plugin from
Added CloudBees Flow version
The CloudBees Backup plugin was considering every folder in the backup folder as a backup file, therefore the plugin was trying to remove the folder when a retention strategy was specified. If the user running the instance has no permission on this folder, or the folder has some content, it fails. If the instance has permissions, the plugin removes such a folder.
Individual Pipeline stages did not have independent results, causing visualizations to report every stage as unstable no matter which stage actually caused the build to become unstable. A new API was created for more granular status tracking in Pipelines. Plugins such as JUnit that set the build result to unstable were updated to use the new API. New Pipeline steps were created that users can use to set the stage result to unstable, see the warnError and unstable steps here: https://jenkins.io/doc/pipeline/steps/workflow-basic-steps/. Additionally, the catchError step was updated to allow optionally setting the stage result. Using these new steps allows Blue Ocean to display exactly which stage caused the build to become unstable.
Upgraded CloudBees Pipeline Stage View Extensions from
2.2 to reference the latest Jackson API plugin.
CloudBees provides you a Helm chart to deploy CloudBees Jenkins Distribution on Kubernetes, making easier the installation. Currently, only Amazon EKS installations are supported. Refer to https://go.cloudbees.com/docs/cloudbees-jenkins-distribution/distro-install-guide/kubernetes/ and https://go.cloudbees.com/docs/general/support-policies/supported-platforms/cloudbees-jenkins-distribution/ for support details.
The Operations Center required a restart to connect to shared agents provisioned via CLI when some optional properties were not fully specified in the agent’s xml configuration. With this fix, creating a shared agent via the CLI no longer requires a restart to connect the agent when specifying an empty
<properties /> element.
If a connected master had a plugin installed that provided a new credential domain requirement type, and the corresponding plugin was not also installed on Operations Center, then no remote credentials were returned when the master queried for them. With this fix, credential domain requirements are deserialized differently on the Operations Center so that missing classes are handled gracefully.
If a directory or file could not be created during a Move/Copy/Promote Operation there were no details informing the user of the cause of the issue. With this fix, the code uses the newer NIO API to enable better error messages in the case of failure.
A blank or white line appeared at the top of the “Teams” view. With this fix, the page design was updated to remove extraneous whitespace.
Credentials cached by client masters could have been lost if the credentials were fetched from the Operations Center as the Operations Center was shutting down. With this fix, the Operations Center signals to client masters that it is shutting down and updated credentials are not available at this time.
During SFTP backups, every single file which needs to be backed up is transferred, one-by-one, to the SFTP server, where it was packed into the backup file destination. Because of this, even the simplest master backup can required hours to be done. With this fix, users now have the option to backup locally and then upload the backup to the SFTP server to decrease backup time.
When certain characters were included in passwords, masking was blocked. With this fix, password masking now masks strings that match the escaped forms of credentials using the escaping algorithms used in sh, bash, zsh, batch, and powershell. This helps fix the issue where shell echoing is enabled (+x) and credentials are included in parameters echoed back.
For "Merge" pipeline runs of Pull Requests on GitHub, Jenkins resorts to cloning the whole repository on the Jenkins Master in order to merge the source and target branches. With this fix, Jenkins uses the GitHub API to get the merged Jenkinsfile from the Pull Request “merge_commit_sha”, causing pipelines for open merge PRs to run on the first scan after upgrade.
Users clicking on an imported template in a catalog were receiving 404 errors. With this fix the link is correctly redirected to the Pipeline Template page when users click on a template in a Pipeline Template Catalog.