openstack/deb-sahara
Code Issues Proposed changes

Update jenkins doc

Browse Source 
We don't gate py26 anymore. Also savanna-ci now have name
Sahara Hadoop Cluster CI

Change-Id: Ie98efa1e2ac135b00aa8927bcc347ac9f34c564d
This commit is contained in:
Vitaly Gridnev 2015-04-07 15:07:54 +03:00
parent d0c7cd4d53
commit 164d32abd7
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/source/devref/jenkins.rst
View File

@ -4,7 +4,7 @@ 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 <https://jenkins.openstack.org/>`_ managed by `Zuul <http://status.openstack.org/zuul/>`_.
Unit tests are checked using both python 2.6 and python 2.7.
Unit tests are checked using 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.
@ -15,6 +15,9 @@ All integration tests are launched by `Jenkins <https://sahara.mirantis.com/jenk
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 <https://sahara.mirantis.com/zuul>`_.
For more information see: `SaharaCI <https://wiki.openstack.org/wiki/Sahara/SaharaCI>`_.
For more information see: `Sahara Hadoop Cluster CI <https://wiki.openstack.org/wiki/Sahara/SaharaCI>`_.
The integration tests result is +1 or -1 to *Verify* column in a code review from *savanna-ci* user.
The integration tests result is +1 or -1 to *Verify* column in a code review from *Sahara Hadoop Cluster CI* user.
You can put *sahara-ci-recheck* in comment, if you want to recheck sahara-ci jobs.
Also, you can put *recheck* in comment, if you want to recheck both jenkins and sahara-ci jobs.