summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorOndřej Šmalec <o.smalec@partner.samsung.com>2020-01-23 11:40:54 +0100
committerOndřej Šmalec <o.smalec@partner.samsung.com>2020-01-23 14:24:01 +0000
commitcb26bd845d1005fcfdef28e599d59d31fc226a55 (patch)
treeab90e7ec95bcc25cea7b8af14c0c8d5d48bfe855 /docs
parentd1d632f7a2beed8cefcd65f9e85670caca09ebf1 (diff)
Replace master branch in BuildGuide
changed master branch to generic <branch> variable. Issue-ID: OOM-2274 Signed-off-by: Ondřej Šmalec <o.smalec@partner.samsung.com> Change-Id: I2fef04e00c6aa096e0fe3cd8d48327c5bf197cc1
Diffstat (limited to 'docs')
-rw-r--r--docs/BuildGuide.rst8
1 files changed, 6 insertions, 2 deletions
diff --git a/docs/BuildGuide.rst b/docs/BuildGuide.rst
index 249d4e85..5b2e2486 100644
--- a/docs/BuildGuide.rst
+++ b/docs/BuildGuide.rst
@@ -10,6 +10,7 @@ This document is describing procedure for building offline installer packages. I
Procedure was completely tested on RHEL 7.6 as it’s tested target platform, however with small adaptations it should be applicable also for other platforms.
Some discrepancies when Centos 7.6 is used are described below as well.
+
Part 1. Preparations
--------------------
@@ -95,7 +96,9 @@ Part 2. Download artifacts for offline installer
::
# clone the OOM repository
- git clone https://gerrit.onap.org/r/oom -b master --recurse-submodules /tmp/oom
+ git clone https://gerrit.onap.org/r/oom -b <branch> --recurse-submodules /tmp/oom
+
+.. note:: replace <branch> by branch you want to build
# docker-images-collector.sh script uses oom/kubernetes/onap/resources/overrides/onap-all.yaml file to find what subsystems
are enabled. By default all subsystems are enabled there. Modify the file if want to drop some subsystems.
@@ -192,8 +195,9 @@ For example:
::
- ./build/package.py https://gerrit.onap.org/r/oom --application-repository_reference master --output-dir /tmp/packages --resources-directory /tmp/resources
+ ./build/package.py https://gerrit.onap.org/r/oom --application-repository_reference <branch> --output-dir /tmp/packages --resources-directory /tmp/resources
+.. note:: replace <branch> by branch you want to build
In the target directory you should find tar files: