Document existing Jenkins setup

[Paul Henshaw]

Provide a brief description (e.g. in a wiki page) of the current state of the Jenkins CI installation and the steps necessary steps necessary to install and configure it.

Currently (if I am not mistaken) the expectation is that tests run by Jenkins complete within a reasonably short time frame (a few minutes).

As described in
 https://blueprints.launchpad.net/openquake/+spec/infrastructure-for-running-long-tests
it would be useful to execute long-running tests in order to facilitate defect detection.

What additional hardware and/or software/configuration changes would be necessary in order to run all long-running demos in a (minimum) parallel environment on the latest master version of oq-engine in a continuous fashion?

How should developers identify which tests are expected to require longer execution times?

Can a single Jenkins instance run tests on multiple machines (e.g. 32bit, 64bit, parallel environment) or are multiple instances required?

[Lars Butler (lars-butler)]

Regarding "additional hardware and/or software/configuration changes" needed in order execute larger jobs:

This work is already captured in the scope of bug # 977810 and bug # 977811.

[Lars Butler (lars-butler)]

>>> Currently (if I am not mistaken) the expectation is that tests run by Jenkins complete within a reasonably short time frame (a few minutes).

The current oq-engine build takes about 20-30 minutes to run all tests. That includes Java tests, python unit tests, and QA tests.

>>> How should developers identify which tests are expected to require longer execution times?

If the test takes a long time to run, then we can say that it has a long execution time.
What constitutes a "long execution time" is up to the discretion of the developers and reviewers.

>>> Can a single Jenkins instance run tests on multiple machines (e.g. 32bit, 64bit, parallel environment) or are multiple instances required?

Technically, yes. Jenkins can execute arbitrary shell commands, which means build/test steps can be execute on a remote machine (via ssh, for example).

[Lars Butler (lars-butler)]

https://github.com/gem/oq-engine/wiki/Continuous-integration-setup-(with-Jenkins)

[Lars Butler (lars-butler)]

The new wiki page is located here: https://github.com/gem/oq-engine/wiki/Continuous-integration-environment