Summary of July 2017 Rolling Releases

We are excited to announce the latest iteration of our rolling releases. Below, are release highlights, from the June 28 release for CloudBees Jenkins Enterprise, CloudBees Jenkins Team and Jenkins. In these releases, CloudBees delivered significant contributions to Jenkins with Blue Ocean 1.1, which are detailed further below.

If you have not done so already, please upgrade your masters and agents to Java 8, all CloudBees products require a Java 8 runtime.

Improvements Across All Products

These improvements apply universally to all of our commercial offerings: CloudBees Jenkins Enterprise, CloudBees Jenkins Platform and CloudBees Jenkins Team.

Feature Benefit

Enhanced release notes
Improved formatting and readability, helps customers identify what changes and components shipped in a release.

This communication improvement helps customers get internal approvals to upgrade their instances, and decide which upgrade they need to take.

New_Rel_Notes.png

 

CloudBees Jenkins Enterprise 1.7.1

Our flagship product, CloudBees Jenkins Enterprise (CJE) solves the automation needs of organizations that need scalability, security, manageability and resiliency capabilities, built on a cloud-native architecture. The theme of this release has been on fixes to improve the overall quality of the product.

Improvement Benefit

Enhanced the default “sizing” of Managed Masters and CloudBees Jenkins Operations Center (CJOC)

With this enhancement in place, customers can see greater stability of the Managed Masters and CJOC, running in a CJE cluster.
Docker images and unauthorized users can not get access to AWS credentials via the metadata server This improvement makes CJE more secure, in that it further tightens the access controls provided to the docker containers running on the CJE cluster.
On Red Hat Enterprise Linux and CentOS installations, cluster logs not visible on UI. With this fix in place, customers can now start to see the cluster logs successfully on CJOC (“Logs” tab).
Recovery operation on a destroyed cluster on vSphere fails. The cluster recovery operation (ability to recover a destroyed cluster) for vSphere based CJE installations now works as intended.
Support for NIO SSH Slaves Plugin using Windows. Customers can use CloudBees updated NIO SSH Slaves Plugin on both Linux and Windows agents improving our support for Windows even further.

CloudBees Jenkins Team 2.60.1.1

CloudBees Jenkins Team is the CloudBees Jenkins distribution with curated, verified integrations and expert support, for organizations in need of a reliable continuous delivery solution. Improvements made in CloudBees Jenkins Team are also included in CloudBees Jenkins Enterprise. This release refreshed several plugins.

Improvement Benefit

CloudBees Assurance Program plugin refreshes

  • The following plugins were updated:
  • Branch API Plugin from 2.0.9 to 2.0.10
  • CloudBees Assurance Plugin from 2.46.2.2 to 2.60.0.1
  • Credentials Binding Plugin from 1.11 to 1.12
  • Display URL API Plugin from 1.1.1 to 2.0
  • GitHub Branch Source Plugin from 2.0.5 to 2.0.6
  • Matrix Authorization Strategy Plugin from 1.5 to 1.6
  • Metrics Plugin from 3.1.2.9 to 3.1.2.10
  • PubSub Light Plugin from 1.7 to 1.8
  • Script Security Plugin from 1.27 to 1.29
  • SSH Slaves Plugin from 1.17 to 1.20
  • Structs Plugin from 1.6 to 1.8

Customers can use the latest and most stable features, minimizing their risk of downtime and the overhead of curating these plugins themselves.

Blue Ocean Improvements

The goal of the Blue Ocean 1.1 release was to reduce technical debt, increases test automation and squash bugs. You can read more about the release on the Jenkins blog.

Improvement Benefit

Fast search
Developers can search for pipelines on the Blue Ocean dashboard.

Blue Ocean does not make use of folders and fast search allows users who make use of many folders and jobs to quickly find their pipeline without having to page through the entire list of pipelines on the dashboard.

Display more than 100 test results
Developers can now see more than 100 test results for a Pipeline run.

This makes Blue Ocean use practical for teams who have invested heavily in testing.

Jump to Activity for any branch
Developers can quickly jump from the Branches tab to the Activity tab and have the branch filtered on the activity.

This makes it more convenient to see historical runs for the branch within the Pipeline which improves the developers ability to trace down problems.

Trigger reasons
Developers can quickly differentiate between pipeline runs that have been manually triggered and by who, triggered automatically by a commit or triggered by any other means.

This makes it easier to see why the pipeline was run, which is essential when tracing changes across runs of the pipeline when there are problems

Blocked pipeline runs
Pipelines can be blocked from execution for a variety of reasons, including waiting for executors or other resources to become free. Developers can see from the Pipeline Activity, Branch and Result screen why the pipeline is blocked.

 Helps the developer understand why their pipeline is not running and if seen often, to increase build resources to reduce feedback time.
Branch filter ordering
Branch filter Pipeline Activity shares the same ordering as the Branch tab.
As the Branch tab and Branch filter are ordered by personal relevancy, it makes it much easier for the developer to filter by a branch they are interested in without having to search in the branch filter list.
Custom Pipeline run name and description
Developers authoring Pipeline scripts can set a custom name and description for any Pipeline run. This feature is commonly used to name or describe a pipeline run that is meaningful in their release management workflow.
For example, a developer can set the run name to the release version "1.1" and set a meaningful description "Final release".
Allows labeling of pipeline runs according to specific needs of the team which improves identification of special runs of the pipeline.
Docker distribution improvements
Blue Oceans Docker distribution is automatically published for every LTS release of open source Jenkins to ensure
This ensures users of the docker image receive the latest improvements, bug and security fixes being delivered in open source

Open Source Improvements

CloudBees provides +80% of the commits to the Jenkins community. Some of the most watched issues in issues.jenkins-ci.org have been resolved with this release. These features are technical but  advance the ability of Pipeline to become the primary job type in Jenkins.

Improvements Benefit

Support for Groovy Methods requiring closures in Pipeline such as .each, .collect, .inject, etc.
It is now possible to use idiomatic Groovy methods in Scripted Pipeline and Shared Libraries.

This simplifies the creation of Shared Libraries that rely on Scripted Pipeline. Developers can use native Groovy methods to craft well-formed libraries with fewer workarounds.

Update Pipeline SCM Plugin integration

The same SCM information that users of Freestyle jobs expect to see such as environment variables are readily available in Pipeline.

This will make the transition to Pipeline from Freestyle easier for users and provide more information inside Pipelines for new users.

Support for Multiple and Alternative Jenkinsfiles in the same repository

The Jenkinsfile has become a standard way of building Pipeline as code. We now support adding multiple Jenkinsfiles to each repository to increase the number of Pipelines even further.

Allowing users to create multiple Jenkinsfiles inside one repo opens the doors to many more use cases that have been expressed by larger development teams.

Support for Windows PowerShell in Pipeline 

 

Microsoft recommends using PowerShell for all command line instructions on Windows. This update dramatically improves Jenkins Pipeline as a platform for testing and automation on Windows agents.

Allow users to combine Jenkinsfile Properties and UI Properties

Users can now use both Jenkinsfile properties and UI driven job properties together in the same configuration.

It is easier for users to reuse Jenkinsfiles across multiple Pipelines that required configuration changes and makes Pipeline configuration easier for users coming from a Freestyle background.

Release Notes

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.