sgode/docsportal
1
0
Fork 0
forked from docs/docsportal
Code Issues Pull Requests Packages Projects Releases Wiki Activity

add additional faq informations

Browse Source
This commit is contained in:
Tino Schreiber 2023-02-15 12:00:10 +00:00
parent b79d39200e
commit 049c8b9c5a
2 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
doc/source/internal/helpcenter_training/faq/faq_images/gate_label.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 141 KiB

12
doc/source/internal/helpcenter_training/faq/how_can_the_docs_be_deployed_to_pre-prod_and_prod_and_who_will_be_the_responsible_to_do_that.rst
View File

@ -3,3 +3,15 @@ How can the docs be deployed to PRE-PROD and PROD and who will be the responsibl
============================================================================================= =============================================================================================
By triggering the label "**gate**" on gitea/github the respective automated jobs will trigger final merge and build of the documentation as well as publishing of the documentation to respective portal (PREPROD/PROD). Responsibility can be addressed to the labelling permission. Remaining stuff is in hands of zuul automation. By triggering the label "**gate**" on gitea/github the respective automated jobs will trigger final merge and build of the documentation as well as publishing of the documentation to respective portal (PREPROD/PROD). Responsibility can be addressed to the labelling permission. Remaining stuff is in hands of zuul automation.
**Prerequesits to set the Gate label:**
1) Confirmity check of Zuul is successful (Zuul approval).
2) Approval of Pull Request by Squad member is there.
If one of these prerequesits is not there. The Zuul pipeline will not start to work and to release the document.
**How to set the Gate label:**
.. image:: faq_images/gate_label.png