zuul
/
zuul
Code Issues Proposed changes

Remove cross-project-gating howto 

This howto has no instructional content.  Retaining it may mislead
users.

Change-Id: I5594bfa3e225ee94c20c9bb8df9ddb3c1483e1bf
This commit is contained in:
James E. Blair 2021-12-07 09:33:17 -08:00
parent 6ce0df6079
commit 61c6a9fc29
3 changed files with 2 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
doc/source/howtos/cross-project-gating.rst
View File

@ -1,24 +0,0 @@
:title: Cross Project Gating
.. _cross-project-gating:
Cross Project Gating
====================
The following sections describe how to test future state of cross projects
dependencies.
Python
------
Python project's requirements are pulled from external source by default, and
the zuul-jobs tox playbook implement a special task to ensure the job required
projects are installed from the zuul src_root so that the gate effectively test
in flight project's state.
Packaging
---------
Similarly, packaging project, where tests are performed using the final binary
artifacts, would need to inject a local repository to ensure the test is using
the change as prepared by Zuul.

1
doc/source/howtos/index.rst
View File

@ -5,7 +5,6 @@ How-To Guides
:maxdepth: 1
zuul-from-scratch
cross-project-gating
pti
badges
matrix

4
doc/source/howtos/pti.rst
View File

@ -210,5 +210,5 @@ test projects as they are prepared by Zuul. For example, the
org-integration-test playbook need to ensure the client and server are installed
from the zuul src_root.
This is called sibbling installation, and it is critical piece to ensure cross
project gating. Check out the recommended practices :ref:`cross-project-gating`.
This is called sibling installation, and it is a critical piece to ensure cross
project gating.