Imagine, you have several environments: developer-integration-test component-integration-test system-integration-test end-to-end-test production-test production and so on… And for all these environments you will have to serve differently configured artifacts. A simple way to achieve this is via Maven-filtering.
Nice idea, to have an aggregator for (often too detailed) ci-server-views. CI-Eye can aggregate Jenkins, Hudson and Teamcity. With using this, you could put some nice 40″ displays into the developers-rooms and everybody can see the red… better green builds 🙂 A nice addon for „tool-driven-development“ and worth to have a further look: https://github.com/netmelody/ci-eye/
Sometimes its hard to realize, that reading the documentation is not only „not so important“… it is quite essential. Just to remember: the argument for setting the url-path of jenkins/hudson ci-installation is called „prefix“. So use the „–prefix=“/jenkins“ to modify the jenkins/hudson-url. source: https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins
just to remember:https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+RedHat+distributions for setting arguments on jenkins-start look at /etc/sysconfig/jenkins… there is no jenkins.xml in $JENKINS_HOME like under windows-os.