Status: Open (View Workflow)
It's currently difficult to make changes to the Blue Ocean CSS because it is compiled by the plugin when a release is prepared. Right now this makes the Blue Ocean CSS difficult to modify for theming purposes. Another plugin should be able to override any of the colors defined in `variables.less` to create a new "Theme" for Blue Ocean. It would also be nice if Blue Ocean made it easy to replace the logo with a custom logo.
- Make it easy to build the CSS based on of a primary brand color or two. Less allows you to define colors that have a relationship to with another. For example, the primary theme could define one color for the header (blue) and define the selection color to be a tint of the header (light blue). A derived theme could then specify it’s own header color (green) and the selection color would be automatically adjust to a tint of the header (light green). If colors are defined to have a relationship with each other it makes it easy for a theme to declare slight adjustments to the main theme without specifying all of the color values (which is harder to maintain as the base theme changes).
- Make it easy to replace the logo with a custom logo. The theme should be able to provide one image for the entire logo, or a logo mark and text (for example, CJE has a 24x24 pixel logo mark with the text “CloudBees Jenkins Enterprise”). The provided logo (or logo mark) could be a gif, PNG, SVG.
I've attached an example theme showing how CloudBees Jenkins Enterprise modifies the Blue Ocean theme to make the header dark teal. The goal of this story is to make it easy for the a plugin to supply:
- A Logo mark
- Logo text (In this example: “CloudBees Jenkins Enterprise”)
- A header background color (In this example: #4e7c91)
And everything is adjusted automatically, including the buttons and the selection colors.
Our current approach for CJE accomplishes this by adding an additional stylesheet that adds rules to override the generated Blue Ocean CSS (bad approach). This is problematic because the CSS in the upstream Blue Ocean package can change without warning and we run the risk of having to re-theme components to get them to use the CloudBees theme.
It would be much easier if we could supply our own “variables.less” and the Blue Ocean CSS would be generated based on our own variables.
- JDL and other plugins export the less rather than compiled CSS
- Blue Ocean compiles and serves less at runtime
- We can build a servlet or something based on lesscss-java
- is duplicated by
JENKINS-49081 Support for Simple Theme Plugin in Blue Ocean
- links to
We are using Blue Ocean with generic pipelines and custom backend (custom approvals & audits via rest calls) and a way to customize the main UI will be very useful. Just like Brandon, we use colors to help some users easily identify Test vs Production Environments.
We use Jenkins Blue Ocean for ci with custom pipeline libraries that do a lot a complex "sh" step call. Each and everyone of theses steps have a custom label that I would like to use as the step name.
Basically that only mean overriding result-item-label-name and result-item-label-name classes.
It would be very convenient to be able to load a custom CSS (that replace or overrride the existing one) instead of having to recompile the plugin
Is there any known timeline on when this might be implemented? We would appreciate this feature a lot.
There is not any known timeline when this might be implemented abdennour.
Jeremy Hartley stated in a Nov 2019 message to the Jenkins Developers mailing list:
We have started a project to revamp the Jenkins User Experience and launched a new User Experience Special Interest Group (SIG) to involve the open source community in this process.
CloudBees does not believe that Blue Ocean is the most appropriate vehicle with which to make these changes. As such, we will focus on alternative approaches and we will not be working on any major new functionality within Blue Ocean.
As we implement improvements to the Jenkins UI and UX, the Blue Ocean pipeline experience will remain relevant to users for quite some time. The work on the new UX will be prioritised and due to the relative modernity of the Blue Ocean pipeline UX, it is not a candidate to be replaced early on in the process. During this time we will selectively address significant security issues and functional defects.
As a part of the Jenkins OSS project, we encourage community contributions that resolve functional issues and add small enhancements to Blue Ocean. We intend to merge worthy community PRs and release these at a regular cadence.
We use Jenkins in the same ways as brandonfryslie with different Banner colours per environment (mostly just red banner for Production).
As the default view is still the legacy UI it is not a concern for us yet but definitely a nice v2 feature.