From 184a87be2b62cfeb6c7234b1da09c462e1008a46 Mon Sep 17 00:00:00 2001 From: Markos Chandras Date: Mon, 27 Nov 2017 15:09:24 +0000 Subject: xci: Drop OPNFV_RELENG_DEV_PATH variable The OPNFV_RELENG_DEV_PATH variable was used to point to a releng-xci development repository. However, people normally set the current directory as the development one and they almost always want to test the current code in XCI. Using an secondary releng-xci tree as development repo is a very obscure case and it normally complicates things. As such, let drop this option and always use the current repository for development purposes. Change-Id: If111bf29a32a5f6ea28694f191645af0c6a87abc Signed-off-by: Markos Chandras --- docs/xci-user-guide.rst | 7 ------- 1 file changed, 7 deletions(-) (limited to 'docs/xci-user-guide.rst') diff --git a/docs/xci-user-guide.rst b/docs/xci-user-guide.rst index 11321383..7a411257 100644 --- a/docs/xci-user-guide.rst +++ b/docs/xci-user-guide.rst @@ -313,13 +313,6 @@ executing the script. The current user variables can be seen from `user-vars `_ file located in releng-xci repository. -The variables can also be set directly within the file before executing -the sandbox script. If you do this, you need to set ``$OPNFV_RELENG_DEV_PATH`` -environment variable where the releng-xci repo is located on your host which -you modified the files in. - -| ``export OPNFV_RELENG_DEV_PATH=/path/to/releng-xci/`` - Pinned Versions --------------- -- cgit 1.2.3-korg