fix(ci): pass the metadata DB to per-minor reindexes and fail on errors #234
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/explicit-metadata-db-reindex"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Step 1 of rpkgs/bincraft#211: pass the metadata database explicitly so bincraft can drop its implicit production defaults.
Changes
metadata_db_*explicitly to every per-minorupload_package_index()call inreindex.yaml,process-updates.yaml,weekly-rebuild-reindex.yaml,build-all-versions.yamlandprune-stale-flat-binaries.yaml.|| truein those per-minor loops with a list of failed minors: every minor is still attempted, then the step exits 1 naming the ones that failed.build-all-versions.yamlthePGPASSsecret. It never had it, so its per-minor reindexes always aborted and|| truehid that.process-updates.yamlandprune-stale-flat-binaries.yamleven when a reindex failed, asreindex.yamlandweekly-rebuild-reindex.yamlalready do, because the generic index was still replaced.local/repair-built-stamp.Rpasses the database too, and fails once all minors are tried instead of only printing the error.The generic (non-per-minor) calls are unchanged: they never read the database.
Behaviour change
A per-minor reindex that fails now turns the pipeline red instead of passing silently.
Expect build-all-versions runs to start reindexing per-minor slots for real, since they now have the password.
Ordering
Merge this before rpkgs/bincraft's companion PR is released:
local/install-bincraft.Rinstalls the latest bincraft tag, and the explicit arguments work with both the current and the next release.