modules/fm-orchestrator
1
0
Fork 0
mirror of https://pagure.io/fm-orchestrator.git synced 2026-04-24 18:52:25 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Remove Greenwave Code

Browse Source 
No implementations of MBS are using Greenwave, and there are no current plans
to do so. Koji Resolver will be sufficient for any usecase dependent on gating.
This commit is contained in:
Brendan Reilly
2022-01-06 13:46:25 -05:00
parent 24e1efd394
commit 4a30847bea
20 changed files with 12 additions and 836 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/GATING.rst
View File

@@ -1,20 +1,8 @@
Modules gating using Greenwave
==============================
Modules gating
==============
Every successfully built module is moved to the ``done`` state. Modules in this state cannot
be used as a build dependency for other modules. They need to be moved to the ``ready`` state.
By default, MBS moves the module from the ``done`` state to the ``ready`` state automatically,
but MBS can also be configured to gate the ``done`` to ``ready`` state transition using
`Greenwave <https://pagure.io/docs/greenwave/>`_.
When Greenwave integration is configured, the following additional MBS features are enabled:
- When the module is moved to the ``done`` state, Greenwave is queried to find out whether
the module can be moved to the ``ready`` state instantly.
- If the module cannot be moved to the ``ready`` state yet, MBS keeps the module build in the
``done`` state and waits for a message from Greenwave. If this message says that all the
tests defined by Greenwave policy have passed, then the module build is moved to the ``ready``
state.
- MBS also queries Greenwave periodically to find out the current gating status for modules
in the ``done`` state. This is useful in case a message from Greenwave was missed.
By default, MBS moves the module from the ``done`` state to the ``ready`` state automatically.
The Koji resolver, if used, will handle gating naturally.