Jenkins Community Releases Blue Ocean
April 05, 2017

The Jenkins project, comprised of a community of practitioners using Jenkins, announced the official release (1.0) and general availability of Blue Ocean, its new UX implementation.

The anticipated launch of Blue Ocean brings a new user experience to Jenkins based on a personalized, modern design that allows users to graphically create, visualize and diagnose continuous delivery pipelines. This is more than just putting a modern face on Jenkins: Blue Ocean re-imagines the Jenkins user experience by enabling teams to more easily adopt continuous delivery.

CloudBees, Inc., the hub of enterprise Jenkins and DevOps, founded the Blue Ocean project and subsequently open sourced the software.

With the official release of Blue Ocean, Jenkins now allows any member of a DevOps team to adopt continuous delivery without having the expert knowledge previously required to use Jenkins.

Continuous delivery pipelines are inherently complex, making it difficult for team members – from developers to IT operations to management – to get a common understanding of the progression of software through the pipeline. Blue Ocean simplifies the development of software pipelines by allowing developers to create them with a visual pipeline editor and then visualize the process flow in an intuitive way, such that the whole organization, not just developers, can understand it.

Blue Ocean naturally fosters collaboration by providing a common view of the end-to-end pipeline that all team members can understand.

Using Blue Ocean, team members gain a graphical overview of the entire pipeline, enabling them to quickly identify issues and then drill down to find the source of the problem. Blue Ocean is underpinned by Pipeline as Code which enables the pipeline definition to be stored with the application code and infrastructure as code; allowing teams to reproduce previous configurations and processes easily when things go wrong.

Key features include:

- Visual Pipeline Editing - Team members of any skill level can create continuous delivery pipelines from start to finish using the intuitive and visual pipeline editor. No code or text editing is required. Anyone can create sophisticated pipelines with just a few clicks.

- Pipeline Visualization - Enables teams to visually represent pipelines in a way anyone in the organization can understand - whether technical or not, improving clarity into the continuous delivery process for the whole organization.

- Pinpoint Troubleshooting - Blue Ocean enables teams to locate automation problems instantly, without endlessly scanning through logs or navigating through many screens.

- GitHub and Git Integration - Pipelines are automatically created and run for all feature branches and pull requests, with their status reported back to GitHub. The whole team has visibility into whether changes need work or are good to go. Blue Ocean provides native, in-depth integration with Git.

- Personalization - Team members can make Jenkins their own by customizing their dashboard so that they only see the pipelines that matter to them.

- Built with and for Declarative Pipeline - Any pipeline created with the visual editor can also be edited in your favorite text editor bringing all the benefits of Pipeline as Code.

The Latest

April 27, 2017

In a movement that has gained momentum as quickly as DevOps has, it's always good to stop from time to time and evaluate where we are, where we have come from, and where we are going. We asked four industry experts some questions about the progress of ALM and DevOps ...

April 26, 2017

It's easy to ignore downtime. But ignoring downtime is a surefire way to upset your customers and your colleagues. More and more, teams need to think about shipping stellar experiences. Proper incident response is a great place to start ...

April 24, 2017

The expectation of regular software updates – it's what developers are tasked with, and what users expect and demand. Increased functionality, better performance, and fewer bugs – often in a week or less. Automation of critical processes such as QA can help meet the gargantuan task of constant updates, but it can also send your software into a death spiral of user abandonment unless deployed correctly ...

April 20, 2017

One could argue that testing is the most important phase of an IT project. It's also time-consuming and expensive. It's essential to strike a balance between an IT testing program that ensures a quality product and the cost-to-value ratio of your project. But when you're dealing with replatforming projects, how much testing is enough testing? ...

April 18, 2017

Whether through formal methods such as classroom or virtual training, job shadowing, and mentoring; or through informal methods such as team discussions or presentations, teaching needs to be a frequent element of team integration. It is a given that IT and business teams have difficulty understanding each other without a common taxonomy. Even teams within IT often fail to understand each other ...

April 17, 2017

Although DBAs fortunately have the rare ability to bridge the gap between development and operations, they have been detrimentally overlooked in many companies that deploy DevOps practices. A DBA's ability to interrogate code and construct a resilient, well–performing database environment uniquely defines the capabilities needed for DevOps – leaving me perplexed about why DBAs were not one of the first operations team members asked to join the DevOps movement ...

April 12, 2017

DEVOPSdigest asked experts across the industry — including analysts, consultants and vendors — for their opinions on the best way for a development or DevOps team to become more Agile. Part 5, the final installment in this series, provides tips on empowering people ...

April 10, 2017

DEVOPSdigest asked experts across the industry for their opinions on the best way for a development or DevOps team to become more Agile. Part 4 covers DevOps technologies ...

April 07, 2017

DEVOPSdigest asked experts across the industry for their opinions on the best way for a development or DevOps team to become more Agile. Part 3 provides some tips for getting started and gaining feedback ...

April 05, 2017

DEVOPSdigest asked experts across the industry for their opinions on the best way for a development or DevOps team to become more Agile. Part 2 covers processes including automation, continuous delivery and testing ..

Share this