From 70fccc37b81a0aeca7a7a5a5d49ac483fb2592e0 Mon Sep 17 00:00:00 2001 From: Anton Medvedev Date: Oct 02 2025 12:11:55 +0000 Subject: This is part of releng repo refactoring -> find_failures.py Signed-off-by: Anton Medvedev --- diff --git a/modules/release_guide/pages/sop_mass_rebuild.adoc b/modules/release_guide/pages/sop_mass_rebuild.adoc index 74eb7ba..b1cf9ea 100644 --- a/modules/release_guide/pages/sop_mass_rebuild.adoc +++ b/modules/release_guide/pages/sop_mass_rebuild.adoc @@ -127,7 +127,7 @@ mass-rebuild.py:: ** target * {blank} + -find-failures.py:: +find_failures.py:: ** buildtag ** desttag ** epoch @@ -194,7 +194,7 @@ ____ The community has a very high interest in the status of rebuilds and many maintainers will want to know if their build failed right away. The -`find-failures.py` and `need-rebuild.py` scripts are designed to update +`find_failures.py` and `need-rebuild.py` scripts are designed to update publicly available URLs for stakeholders to monitor. ===== @@ -213,9 +213,14 @@ $ tmux .... ____ . Clone or checkout the latest copy of the -https://pagure.io/releng[releng git repository] -. {blank} +https://pagure.io/releng[releng git repository] and move to location that contains `find_failures.py` script. + +____ +.... +$ cd releng/scripts_new/release-process/mass-rebuilds/ +.... +____ +. {blank} Set Up the Rebuild Failures Notification Web Site:: The `find_failures.py` script discovers attempted builds that have failed. It lists those failed builds and sorts them by package owner.