openstack/deb-sahara
Code Issues Proposed changes
fa1a5217fd
deb-sahara/doc/source/devref/jenkins.rst
Denis Egorenko badf474420 Fix Sahara CI links 
* fix wrong URL to Jenkins
* add link to Sahara Zuul status page
* add link to Sahara CI wiki page

Change-Id: I7e3a61d3cd5914a438998e5bbe9772d5145a97be
2014-06-18 17:27:17 +04:00

1.3 KiB
Raw Blame History

Continuous Integration with Jenkins

Each change made to Sahara core code is tested with unit and integration tests and style checks flake8.

Unit tests and style checks are performed on public OpenStack Jenkins managed by Zuul. Unit tests are checked using both python 2.6 and python 2.7.

The result of those checks and Unit tests are +1 or -1 to Verify column in a code review from Jenkins user.

Integration tests check CRUD operations for Image Registry, Templates and Clusters. Also a test job is launched on a created Cluster to verify Hadoop work.

All integration tests are launched by Jenkins on the internal Mirantis OpenStack Lab. Jenkins keeps a pool of VMs to run tests in parallel. Even with the pool of VMs integration testing may take a while. Jenkins is controlled for the most part by Zuul which determines what jobs are run when. Zuul status is available by address: Zuul Status. For more information see: SaharaCI.

The integration tests result is +1 or -1 to Verify column in a code review from savanna-ci user.