Updated variable name, updated manifest file (#20)

IceCI · Aug 20, 2020 · a576b9c · a576b9c
1 parent 7323bd1
commit a576b9c
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/source/pages/pipelines/building_template.rst b/source/pages/pipelines/building_template.rst
@@ -113,8 +113,8 @@ Available variables
 
   Example value: ``VXBkYXRlICdSRUFETUUubWQnCg==``
 
-.. envvar:: ICECI_GIT_TAG_OR_BRANCH
+.. envvar:: ICECI_GIT_EVENT_NAME
 
-  The name of the current git branch or tag - the value depends on which type of event triggered the build.
+  The name of the current git branch, tag or pr - the value depends on which type of event triggered the build.
 
   Example value: ``master``
diff --git a/source/pages/quickstart.rst b/source/pages/quickstart.rst
@@ -44,13 +44,13 @@ You can use a handy all-in-one manifest to install IceCI. Applying it in your cl
 .. code-block:: bash
 
   kubectl apply -f https://raw.githubusercontent.com/IceCI/IceCI/master/manifests/crds.yaml
-  kubectl apply -f https://raw.githubusercontent.com/IceCI/IceCI/master/manifests/one-node.yaml
+  kubectl apply -f https://raw.githubusercontent.com/IceCI/IceCI/master/manifests/minikube.yaml
 
 Once all the applications are running, you're all ready to go.
 
 
 .. note::
-    Apart from the one-node file, kustomize files for all components, and examples of setup can be found as separate files in the IceCI `GitHub repository <https://github.com/IceCI/IceCI>`_
+    Apart from the minikube file, kustomize files for all components, and examples of setup can be found as separate files in the IceCI `GitHub repository <https://github.com/IceCI/IceCI>`_