From aa7b0c7c6a3616cde997ad15f6313be574178537 Mon Sep 17 00:00:00 2001 From: Anton Medvedev Date: Oct 02 2025 12:15:01 +0000 Subject: ref: This is part of releng repo refactoring -> need_rebuild.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..6109f27 100644 --- a/modules/release_guide/pages/sop_mass_rebuild.adoc +++ b/modules/release_guide/pages/sop_mass_rebuild.adoc @@ -134,7 +134,7 @@ find-failures.py:: * mass-tag.py * {blank} + -need-rebuild.py:: +need_rebuild.py:: ** buildtag ** target ** updates @@ -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. ===== @@ -229,7 +229,7 @@ $ while true; do ./find_failures.py > f{rawhide}-failures.html && cp f{rawhide}- . {blank} + Set up the Site for Packages that Need Rebuilt:: - The `need-rebuild.py` script discovers packages that have not yet been + The `need_rebuild.py` script discovers packages that have not yet been rebuilt and generates an html file listing them sorted by package owner. This gives external stakeholders a rough idea of how much work is remaining in the mass rebuild. @@ -237,7 +237,8 @@ Set up the Site for Packages that Need Rebuilt:: [source,subs="attributes+"] .... -$ while true; do ./need-rebuild.py > f{rawhide}-need-rebuild.html && cp f{rawhide}-need-rebuild.html /mnt/koji/mass-rebuild/f{rawhide}-need-rebuild.html; sleep 600; done +$ cd releng_repo/scripts_new/release-process/mass-rebuilds/ +$ while true; do ./need_rebuild.py > f{rawhide}-need-rebuild.html && cp f{rawhide}-need-rebuild.html /mnt/koji/mass-rebuild/f{rawhide}-need-rebuild.html; sleep 600; done .... =====