From d67092a1de9f970d0f2481d92cd64d4d493936af Mon Sep 17 00:00:00 2001
From: Bruno Goncalves <bgoncalv@redhat.com>
Date: Apr 17 2020 08:45:30 +0000
Subject: add information how to rebuild container image on dist-git pipeline


---

diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
index a186b51..9a61169 100644
--- a/modules/ROOT/nav.adoc
+++ b/modules/ROOT/nav.adoc
@@ -11,6 +11,8 @@
 ** xref:tests.adoc[Tests]
 ** xref:pipeline.adoc[Pipeline]
 ** xref:gating.adoc[Gating]
+* Maintenance
+** xref:rebuild-container-image.adoc[Rebuild container images]
 * More
 ** xref:test-case-relevancy.adoc[Test Case Relevancy]
 ** xref:source-git.adoc[Source Git]
diff --git a/modules/ROOT/pages/rebuild-container-image.adoc b/modules/ROOT/pages/rebuild-container-image.adoc
new file mode 100644
index 0000000..d4a4e09
--- /dev/null
+++ b/modules/ROOT/pages/rebuild-container-image.adoc
@@ -0,0 +1,25 @@
+:toc:
+
+= dist-git pipeline - rebuild container images =
+
+== When rebuild the image ==
+
+There are cases where it is necessary to rebuild the container image used by the pipeline.
+For example if some package needs to be updated, like for example:
+
+* rpm-build
+* standard-test-roles
+
+== How to ==
+
+. Open https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-stage-container-image-build/[fedora-stage-container-image-build] (make sure you are logged in)
+. Click on build with parameters (the image name by default is already fedoraci-runner)
+. Once the build start it will create a new container build and tag it as candidate
+. Once the image is built a build on https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-rawhide-stage-pr-pipeline/[fedora-rawhide-stage-pr-pipeline] is created to validate the image
+. If the jenkins build succeeds the image will be tagged as stable and the pipeline will from now on use it
+
+== Troubleshooting ==
+
+. If the job fails the initial point to search for the cause is to look at the build on https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-stage-container-image-build/[fedora-stage-container-image-build] job.
+. If it failed before running https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-rawhide-stage-pr-pipeline/["fedora-rawhide-stage-pr-pipeline"] stage it is likely a problem creating the container image checking it on https://console.apps.ci.centos.org:8443/console/project/continuous-infra/browse/builds/fedoraci-runner?tab=history[openshift] could help.
+. If the problem was during https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-rawhide-stage-pr-pipeline/["fedora-rawhide-stage-pr-pipeline"] then is necessary to check its build log.