Jenkins

In this post I will describe a solution to add a portal page, a common header and a dynamic panel to each of the three tools Jenkins, SonarQube, and Nexus. Those modifications lead to a better visual integration and intensifies the impression that the tools belong together. As a pre-requisite you need an Apache HTTP server, configured as reverse proxy and the tools accessible via the following context path: /jenkins /sonarqube /nexus The folder structure which contains the portal page and the customization fragments looks like this: ...

While trying to apply a unified visual layout to the tools Jenkins, SonarQube, and Nexus I learned that there are some plugins available, but none of them really fits the intended purpose. Jenkins has no easy way of changing its appearance and the Simple Theme plugin comes only close to what is needed. In SonarQube there is a Branding plugin with which you can display an image at the top of each page, but that’s basically all. The Nexus plugin to change the Sonatype Nexus logo is available for the professional version only, but buying the professional version just for being able to change the logo is not really an option. ...