Customizations

Not all the default configuration settings might match your requirements. Because of that and also due to our own different [[environments|Environments] we allow customizations to some of the settings in Jenkins.

Changing the version of Mozmill

If you need to specify an alternate version of Mozmill to use, you can change the value associated with the MOZMILL_AUTOMATION_VERSION environment variable. This can be found in http://localhost:8080/configure under the section headed "Global properties".

E-mail notifications

By default there is no e-mail address for notifications to be sent. In our production system we have these sent to the mozmill-ci mailing list. If you would like to enable notifications locally (this can be useful during testing) you will have to specify the recipient e-mail address for the NOTIFICATION_ADDRESS environment variable. This can be found in http://localhost:8080/configure under the section headed "Global properties".

Jenkins URL

If you intend to connect to this Jenkins instance from another machine (for example connecting additional nodes) you will need to update the Jenkins URL to the IP or DNS name. This can be found in http://localhost:8080/configure under the section headed "Jenkins Location".

Adding new Nodes

To add new Jenkins slaves to your master you have to create new nodes. You can use one of the example nodes (Windows XP and Ubuntu) as a template. Once done the nodes have to be connected to the master. Therefore Java has to be installed on each node first.

Windows:

Go to www.java.com/download/ and install the latest version of Java JRE.

Also make sure that the UAC is completely disabled, and the screensaver and any energy settings have been turned off.

Linux (Ubuntu):

Open the terminal or any other package manager and install the following packages:

sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java7-installer

Also make sure that the screensaver and any energy settings have been turned off.

OS X

Go to www.java.com/download/ and install the latest version of Java JRE.

Also make sure that the screensaver and any energy settings have been turned off.

Connecting the slave node

After Java has been installed open the appropriate node within Jenkins from the nodes web browser like:

http://IP:8080/computer/windows_xp_32_01/

Now click the Launch button and the node should automatically connect to the master. It will be used once a job for this type of platform has been requested by the Pulse consumer, or you trigger a build manually.

Using the Jenkins master as executor

If you want that the master node also executes jobs you will have to update its labels and add/modify the appropriate platforms, e.g. master mac 10.7 64bit for Mac OS X 10.7.

Please note, that instead of the master node we propose to use the existent dummy node as executor. You can connect to it from the same machine.

Job priorities

To allow Mozmill tests to be executed immediately for important builds (e.g. release and beta) priorities are necessary. The same applies to the type of testrun, where some have higher priority.

trigger_ondemand

1099

ondemand	1000
release-mozilla-release	800
release-mozilla-esr(CUR)	700
release-mozilla-esr(LAST)	600
release-mozilla-beta	500
mozilla-esr	400
mozilla-central	300
mozilla-aurora	200
mozilla-project	100

update	60
functional	50
endurance	40
remote	30
addon	20
l10n	10

The higher the priority value, the higher the priority the job will have in the queue. For example, mozilla-central_endurance will have a value of 340 (300 + 40) and will therefore be executed before mozilla-aurora_endurance, which will have a value of 240 (200 + 40).