openstack/nova
Code Issues Proposed changes

Document experimental pipeline in Nova CI

Browse Source 
Add a section in "core-review" to document how experimental pipeline would
be used by Nova developers in order to consume the resources at the
right time.

Change-Id: I5df377032c2fcec18cdf71af2568e028373bcced
This commit is contained in:
Emilien Macchi 2016-10-04 09:30:35 -04:00
parent ddbbf57827
commit 26826bc686
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/source/code-review.rst
View File

@ -195,6 +195,24 @@ Please note:
* We are only talking about the testing of in-tree code. Please note the only * We are only talking about the testing of in-tree code. Please note the only
public API is our REST API, see: :doc:`policies` public API is our REST API, see: :doc:`policies`
Should I run the experimental queue jobs on this change?
========================================================
Because we can't run all CI jobs in the check and gate pipelines, some
jobs can be executed on demand, thanks to the experimental pipeline.
To run the experimental jobs, you need to comment your Gerrit review
with "check experimental".
The experimental jobs aim to test specific features, such as LXC containers
or DVR with multiple nodes. Also, it might be useful to run them when
we want to test backward compatibility with tools that deploy OpenStack
outside Devstack (e.g. TripleO, etc). They can produce a non-voting
feedback of whether the system continues to work when we deprecate
or remove some options or features in Nova.
The experimental queue can also be used to test that new CI jobs are
correct before making them voting.
Database Schema Database Schema
=============== ===============