tooling/release-process/mass-rebuilds
2026-09-08 10:32:59 +05:30
..
find_failures.py Refactor mass rebuild scripts to use dynamic MASSREBUILDS config (#13425) (#13045) 2026-09-08 04:54:25 +00:00
find_FTBFS.py Migration to Forgejo: releng/tooling Pt 1 2025-10-10 12:59:13 +05:30
mass_rebuild.py Refactor mass rebuild scripts to use dynamic MASSREBUILDS config (#13425) (#13045) 2026-09-08 04:54:25 +00:00
mass_rebuilds_info.py Fix default rebuildid crash on incomplete entries and wrong target mapping in need_rebuild.py 2026-09-08 10:32:59 +05:30
mass_tag.py Refactor mass rebuild scripts to use dynamic MASSREBUILDS config (#13425) (#13045) 2026-09-08 04:54:25 +00:00
need_rebuild.py Fix default rebuildid crash on incomplete entries and wrong target mapping in need_rebuild.py 2026-09-08 10:32:59 +05:30
README.md Refactor mass rebuild scripts to use dynamic MASSREBUILDS config (#13425) (#13045) 2026-09-08 04:54:25 +00:00
test_mass_rebuild.py Harden dist-git gating: fix TOCTOU, surface Koji errors, add edge-case tests 2026-09-07 06:21:35 +00:00

Mass Rebuild Tools

Scripts for orchestrating mass rebuilds during Fedora release cycles.

Purpose

Tools that coordinate large-scale package rebuilds, typically performed twice per release cycle for toolchain updates.

Examples of scripts that will be migrated here:

  • Mass rebuild orchestration
  • Rebuild status tracking
  • Bug filing for failed rebuilds

Status: 🚧 Awaiting migration

Usage

The scripts in this directory (find_failures.py, need_rebuild.py, etc.) pull their configuration from the centralized MASSREBUILDS dictionary located in mass_rebuilds_info.py.

By default, the scripts will dynamically calculate and target the latest Fedora release defined in the dictionary.

If you need to target a specific older release, you can override the default behavior using the --rebuildid flag:

python3 find_failures.py # Targets the latest release automatically

python3 find_failures.py --rebuildid f44 # Targets a specific release (e.g., f44)

Note for mass_tag.py: You can still use the legacy -t (target) and -s (source) flags if you need to perform a manual tagging operation outside of a standard release cycle. These flags will override the MASSREBUILDS dictionary configurations.