From: Yolanda Robla <yroblamo@redhat.com>
Date: Fri, 2 Jun 2017 12:37:54 +0000 (+0200)
Subject: Talk about development mode for XCI
X-Git-Tag: 6.0.0~357
X-Git-Url: https://gerrit.opnfv.org/gerrit/gitweb?a=commitdiff_plain;h=c721dd1a75fa44ccfdf8b213b21c11cd50073d3c;p=releng-xci.git

Talk about development mode for XCI

Explain the usage of OPNFV_RELENG_DEV_PATH

Change-Id: I19e3946c9ea78a6bb0521818b58af297a396d80d
---

diff --git a/xci/README.rst b/xci/README.rst
index 0d936653..b65abde9 100644
--- a/xci/README.rst
+++ b/xci/README.rst
@@ -185,6 +185,23 @@ continuously chasing the HEAD of corresponding branches.
 Once a working version is identified, the versions of the upstream components
 are then bumped in releng repo.
 
+==================
+XCI developer tips
+==================
+
+It is possible to run XCI in development mode, in order to test the
+latest changes. When deploying on this mode, the script will use the working
+directories for releng/bifrost/OSA, instead of cloning the whole repositories
+on each run.
+To enable it, you need to export the different DEV_PATH vars:
+
+- export OPNFV_RELENG_DEV_PATH=/opt/releng/
+- export OPENSTACK_BIFROST_DEV_PATH=/opt/bifrost
+- export OPENSTACK_OSA_DEV_PATH=/opt/openstack-ansible
+
+This will cause the deployment to pick the development copies stored at the
+specified directories, and use them instead of cloning those on every run.
+
 ===========================================
 Limitations, Known Issues, and Improvements
 ===========================================