Blue Ocean: Rethinking Jenkins’ user experience
Blue Ocean is reshaping Jenkins’ user experience, modeling and presenting the process of software delivery by transpiring information which is important to development teams with as few clicks as possible without sacrificing the extensibility which is core to Jenkins.
CloudBees’ James Dumay announced the arrival of Blue Ocean in a blog post in late May. 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.
According to Dumay, this project reconsiders Jenkins’ user experience, modeling and presenting the process of software delivery by transpiring information which is important to development teams with as few clicks as possible without sacrificing the extensibility which is core to Jenkins. Although the project is still in the alpha stage of development, the end result should be the following: Jenkins users should be able to install Blue Ocean side-by-side with the Jenkins Classic UI through a plugin. The project is now open source.
Improved user experience
The aim of the UI is to boost clarity, diminish clutter, as well as navigational depth to transform the user experience into a very concise process. The modern visual design offers developers relief throughout their daily usage while screens respond immediately to alterations on the server making manual page refreshes obsolete.
Advanced Pipeline visualizations have built-in failure diagnosis
Pipelines can be visualized on screen alongside steps and logs to enable simplified comprehension of the continuous delivery pipeline. Scrolling through 10,000 line log files has also been made obsolete because one of the perks of Blue Ocean is that it breaks down ther log per step and calls out where the build failed.
Built with Branch and Pull Request in mind
Blue Ocean is aware that modern pipelines use multiple Git branches. All you need to do is drop a
Jenkinsfile into your Git repository which defines the pipeline and Jenkins automatically discovers and starts automating any Branches and validating Pull Requests.
Intelligence is being built into the dashboard, which means that jobs which require your attention appear on the top of the dashboard.