Jenkins Blue Ocean: a deprecated Pipeline UI and what to use instead

What Blue Ocean was built to fix in the Jenkins UI

The classic Jenkins interface is organized around jobs, configuration forms and build history. Blue Ocean is an alternative user experience for that same server, aimed at people who care about the shape of a Pipeline rather than the list of jobs that contain it. The README describes it as providing easy-to-use Pipeline visualization, and the repository is a multi-module Maven project made up of several Jenkins plugins rather than a single artifact.

The audience is narrower than "all Jenkins users". The README points developers at the module READMEs, and the install path it gives is the Jenkins update center, where the plugin is listed under the name BlueOcean beta. That beta label has stayed in the documentation even though releases continued into the 1.27.x line. If you are evaluating this for a team, treat it as a visualization layer on top of an existing controller, not as a reason to choose Jenkins.

The module split that makes Blue Ocean a plugin, not a fork

Blue Ocean ships as a set of Jenkins plugins. The blueocean module is an aggregator, which the README describes as an easy place from which to run Blue Ocean via hpi:run. The dashboard module holds much of the user interface and the extension points, and it is mostly client side JavaScript built with ES6 and React.

On the server side, blueocean-rest defines the REST API contract, and blueocean-rest-impl supplies the default implementation of the core REST APIs. That implementation ships with freestyle job support only. Pipeline and multi-branch job types are handled separately by blueocean-pipeline-api-impl. This split explains a limitation you will notice in practice: what the UI can show depends on which of these plugins is installed and which job type you are looking at. A freestyle job and a multi-branch Pipeline do not travel through the same code path.

blueocean-web bootstraps the UI, integrates the REST API core from blueocean-rest, and serves the core JavaScript libraries. Around those sit integration modules for specific sources and tools, including blueocean-git-pipeline, blueocean-github-pipeline, blueocean-bitbucket-pipeline, blueocean-jira, blueocean-jwt and blueocean-events, plus jenkins-design-language and js-extensions for the front end.

Installing the Blue Ocean plugin and opening the Pipeline view

The README gives the production path first: Blue Ocean is available from the Jenkins update center for Jenkins 2.7.1 and above, listed as the plugin BlueOcean beta, and you let it install its dependencies. There is no separate binary to fetch and no server to run.

If you are working from the repository instead, the README states that a JVM, Maven and Python are the minimum, and that NodeJS is optional because the frontend-maven-plugin installs the correct version of Node locally for each plugin. The first build from the root directory is:

$ mvn clean install

The README notes that on macOS you must install JDK 1.8 or the installation will fail, and that on Windows you need to skip tests:

$ mvn clean install -DskipTests

To run the aggregator plugin locally, the README gives:

$ mvn -f blueocean/pom.xml hpi:run

After that, the README says to open http://localhost:8080/jenkins/blue to start using Blue Ocean, with the classic UI side by side at http://localhost:8080/jenkins. While running in this mode, Jenkins recompiles JavaScript and LESS files for local plugins whose package.json contains an mvnbuild script. That watch behaviour can be turned off with the system property -Dblueocean.features.BUNDLE_WATCH_SKIP=true.

The deprecation is explicit, and the repository says so twice

The README does not soften this. It states that Blue Ocean will not receive further functionality updates, that it will continue to provide easy-to-use Pipeline visualization, and that it will only receive selective updates for significant security issues or functional defects. The repository topics include deprecated and deprecated-unmaintained. Anyone planning a migration should read that as the project's own position, not as community speculation.

The release cadence matches the statement. Releases continue (blueocean-parent-1.27.24 in November 2025, 1.27.25 later that month, and 1.27.26 in August 2026), so the plugin is not frozen, but the README frames what those releases are for. The last push to the default branch was on 2026-08-05, which is recent enough that the repository is not abandoned in the literal sense. Maintenance and feature development are different things here, and the README is clear about which one stopped.

There is a second, quieter limitation in the same document: the browser compatibility section says the goal is for Blue Ocean to run on all browsers on all platforms and that the project is not there yet. It lists Internet Explorer below version 11 on Windows and AmigaOS as known non-working environments. That section has the tone of an unfinished project, which is consistent with the status paragraph above it.

What to use instead, and where the replacement falls short

The README names two alternatives: the Pipeline: Stage View plugin and the Pipeline Graph View plugin, both of which it says are available and offer some of the same functionality. The distinction it draws is important. It describes them as not complete replacements for Blue Ocean, and it encourages community contributions for their continued development.

The practical difference is scope. Blue Ocean is a full alternative interface with its own dashboard, its own REST API layer and its own extension points for React components. The two replacement plugins are visualization additions to the classic Jenkins UI. If what you used Blue Ocean for was watching stages light up during a run, Stage View or Pipeline Graph View is a direct substitute. If you used the Blue Ocean dashboard for editing Pipelines or for its multi-branch navigation, the README does not claim those plugins cover it, and you should assume they do not until you verify it on your own controller.

For Pipeline authoring, the README points elsewhere entirely: the Pipeline syntax snippet generator, which it calls the preferred tool for Jenkins Pipeline creation because it provides online help for the Pipeline steps available in your Jenkins controller and uses the plugins installed there to generate syntax. That is a different answer to a different question than visualization, and it is the one the project currently endorses.

Building Blue Ocean plugins is the weakest reason to start

The developer documentation is candid in a way that should factor into any decision. It says the instructions in the README are for contributors to Blue Ocean and the morbidly curious, and adds: expect refactoring. The extension points it describes are JavaScript extension points that work with React components.

If your goal is to build a Jenkins UI plugin, the README routes you to the generator-blueocean-usain Yeoman starter on npm and to the usual Jenkins plugin tutorial, and it suggests asking in the Gitter room or on the jenkins-ux Google group. But the same document says contributions are encouraged for the replacement plugins instead. Starting new plugin work on a codebase whose own README says it will not receive further functionality updates is a decision you should make with that sentence in front of you.

The build instructions also carry environment constraints worth counting. macOS needs JDK 1.8 specifically, Windows needs -DskipTests, and the Dockerfile states that BlueOcean must be built locally with Maven before the image is built, invoking bin/build-in-docker.sh -m. That Dockerfile copies blueocean/target/plugins into /usr/share/jenkins/ref/plugins, renames .hpi files to .jpi, and runs install-plugins.sh antisamy-markup-formatter matrix-auth, so a container-based evaluation depends on a successful local Maven build first.

Licence and the cost of staying on a deprecated plugin

The repository is MIT licensed, with LICENSE.txt at the top level and a licenses directory alongside it. MIT is permissive, so forking and continuing development is legally straightforward as far as the licence text goes. This is not legal advice, and if you plan to redistribute a modified build you should read LICENSE.txt and the contents of the licenses directory yourself rather than relying on a summary.

The upgrade cost is the more concrete issue. Because the README commits only to selective updates for significant security issues or functional defects, you cannot plan feature work around Blue Ocean, and you cannot assume a fix for a cosmetic or workflow bug will land. The version numbers in the 1.27.x line show that releases still happen, so a pinned version will keep working, but the direction of travel is toward the visualization plugins the README names. Budget for the migration rather than for new Blue Ocean features.

Editorial conclusion

Adopt Blue Ocean only if you already run it and need its Pipeline visualization on an existing controller; the repository topics include deprecated and deprecated-unmaintained, and the README states it will receive selective updates for significant security issues or functional defects only. Do not adopt it for new Jenkins installations or for plugin development, because contributions are instead directed at Pipeline: Stage View and Pipeline Graph View. Before installing anything, check which Jenkins baseline your controller runs, since Blue Ocean is listed for Jenkins 2.7.1 and above, and confirm whether the Pipeline Graph View plugin covers the visualization you actually need.

Frequently asked questions

Official sources

1. jenkinsci/blueocean-plugin on GitHub
2. License: MIT
3. Project website
4. README
5. Releases