Skinning and provisioning Jenkins using a WAR overlay
This recipe describes how to overlay onto the Jenkins WAR file. With a WAR overlay, you can change the look and feel ready for corporate branding and provisioning of home pages. The basic example of adding your own favicon.ico (the icon in your web browser's address bar) is used. It requires little effort to include more content.
Jenkins keeps its versions as dependencies in a Maven repository. You can use Maven to pull in the WAR file, expand it, add content, and then repackage. This enables you to provision resources such as images, home pages, the icon in the address bar called a fav icon, and robots.txt
that affects how search engines look through your content.
Be careful, using a WAR overlay will be cheap if the structure and the graphical content of Jenkins do not radically change over time. However, if the overlay does break the structure, then you might not spot this until you perform detailed functional tests.
You can also consider...