days
-3
-7
hours
-1
-3
minutes
-4
-7
seconds
-2
-4
search

Blue Ocean 1.0 is here — and it’s “more than just perking up Jenkins”

Gabriela Motroc
Blue Ocean 1.0

Blue sea and white fluffy clouds image via Shutterstock

As more organizations adopt Jenkins as their engine for continuous delivery (CD), broader teams with varying degrees of technical skills demand a more bespoke and succinct user interface. Say hello to Blue Ocean 1.0.

CloudBees’ James Dumay announced the arrival of Blue Ocean in a blog post published in 2016. He acknowledged that developers have become increasingly attracted to tools which are not only functional but are also created to fit into their workflow in a seamless way. Jenkins was in need of a top-notch user experience — which is why Blue Ocean came into being.

Blue Ocean 1.0 came one year later but it was worth the wait. James Dumay presented the highlights in a new blog post.

Blue Ocean 1.0 overview

Visual pipeline editing

Continuous delivery pipelines can be created from start to finish, with just a few clicks with the help of the intuitive, visual pipeline editor. Furthermore, pipelines created with the visual editor can also be edited in users favorite text editor bringing all the benefits of Pipeline as Code.

Pipeline visualization

Pipelines can now be visually represented in a way that anyone on the team can understand, thus improving clarity into the continuous delivery process for the entire organization. The visualization will come in handy if you prefer to focus on what the pipeline does, not how it does it.

Pinpoint troubleshooting

Developers can locate automation problems immediately, without having to scan through logs or navigate through screens.

GitHub and Git integration

The entire team can now see if changes need additional work or are good to go. According to Dumay, pipelines are created for all feature branches and pull requests, with their status reported back to GitHub.

Personalization

Last but not least, the dashboard can be customized so that users (a.k.a. team members) only see the pipelines that matter to them. If you want to see the status of any pipeline or branch in Blue Ocean, all you need to do is favorite it and a favorite card will appear on the dashboard.

“Our goal with Blue Ocean is more than just to perk up Jenkins”

Blue Ocean and found out that CloudBees’ goal is “more than just to perk up Jenkins. Jenkins lives in an ecosystem of developer tools that are constantly changing and competing against each other as the needs of the industry change.

For Blue Ocean, it’s important that as the tools in a developer’s toolbox change and the practices change that Jenkins is able to respond and meet the needs of modern developers. Blue Ocean is built for developers – both beginner and expert alike, to make the best use of continuous delivery. Anyone can create a pipeline and easily visualize it, and Blue Ocean makes it easy to diagnose failures within the pipeline.

Read the entire interview here.

Author
Gabriela Motroc
Gabriela Motroc is editor of JAXenter.com and JAX Magazine. Before working at Software & Support Media Group, she studied International Communication Management at the Hague University of Applied Sciences.

Leave a Reply

Be the First to Comment!

avatar
400
  Subscribe  
Notify of