Skip to content

Adapt the documentation to Blue Ocean deprecation #9038

Description

@MarkEWaite

Describe your use-case which is not covered by existing documentation.

Blue Ocean will be deprecated in July 2026 per the CloudBees announcement. I think that the main body of Jenkins documentation should describe Pipeline Graph View rather than describing Blue Ocean. We should retain the Blue Ocean pages for reference by users that are still running it, but should not include Blue Ocean in the primary documentation flow.

The Blue Ocean status entries on the existing pages should be updated to note that it will be deprecated July 2026.

I don't think we should remove the existing pages, but they should not be so prominently visible in the table of contents.

Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.

Blue ocean deprecation has been mentioned in community.jenkins.io posts like:

Blue ocean deprecation has been discussed many times in documentation office hours, including:

Are you interested in contributing a fix?

I'll probably submit an update to the status entries, but am unlikely to implement the full replacement.

Screenshots

Some sample screenshots from the changes:

Image Image Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationJenkins documentation, including user and developer docs, solution pages, etc.

    Type

    Fields

    Priority

    None yet

    Target date

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions