cpu-sig-tracker - Man Page
Track CentOS Proposed Updates (CPU) SIG package state across Koji, GitLab, and JIRA
Synopsis
Description
Track CentOS Proposed Updates (CPU) SIG package state across Koji, GitLab, and JIRA
Options
- -h, --help
Print help
- -V, --version
Print version
Commands
cpu-sig-tracker config
cpu-sig-tracker config [-h|--help]
Set up GitLab and JIRA authentication tokens
- -h, --help
Print help
cpu-sig-tracker dump-inventory
cpu-sig-tracker dump-inventory [-r|--release] [--koji-profile] [--prune] [-v|--verbose] [-h|--help] <-o|--output>
Enumerate packages in a proposed_updates Koji tag and emit a sandogasa-inventory TOML file
- -r, --release <RELEASES>
CentOS release(s) to enumerate, e.g. "c10s" or "c9s,c10s" (CSV or repeated). The Koji tag queried per release is "proposed_updates<N>s-packages-main-release" where N is the major version digit
- -o, --output <OUTPUT>
Output file (sandogasa-inventory TOML). If it exists, merge in the newly-discovered packages; existing entries are preserved
- --koji-profile <KOJI_PROFILE> [default: cbs]
Koji CLI profile (cbs for CentOS Build System)
- --prune
Drop packages from each workload that are no longer tagged in either the `-release` or `-testing` tag for that release. Orphan `[[package]]` entries (metadata blocks for packages no longer referenced by any workload) are left in place so user-entered fields aren't lost
- -v, --verbose
Print progress to stderr
- -h, --help
Print help
cpu-sig-tracker file-issue
cpu-sig-tracker file-issue [--affected] [--expected-fix] [--jira] [--release] [--type] [--note] [--dry-run] [-v|--verbose] [-h|--help] <MR_URL>
File a tracking issue in the proposed_updates GitLab group for a given Merge Request URL
- --affected <AFFECTED>
Affected (currently-tagged) NVR. If omitted, left blank in the issue body; can be filled in later
- --expected-fix <EXPECTED_FIX>
Expected fix NVR once the MR lands and is built
- --jira <JIRA>
Override the auto-extracted JIRA key (e.g. "RHEL-12345"). Useful when the MR description doesn't mention it verbatim
- --release <RELEASE>
Override the release auto-derived from the MR target branch (e.g. `c10s`)
- --type <ISSUE_TYPE>
Apply one of the proposed_updates type labels: enhancement, bugfix, arch-enablement, security
Possible values:
- enhancement
- bugfix
- arch-enablement
- security
- --note <NOTE>
Free-form context note prepended to the issue body as a lead paragraph before the structured metadata
- --dry-run
Print the issue that would be filed and exit without making any GitLab API calls
- -v, --verbose
Print progress to stderr
- -h, --help
Print help
- <MR_URL>
Full Merge Request URL to track, e.g. `gitlab.com/redhat/centos-stream/rpms/xz/-/merge_requests/42` (with the https:// scheme)
cpu-sig-tracker list-issues
cpu-sig-tracker list-issues [-i|--inventory] [--release] [--package] [--adopt] [--json] [-v|--verbose] [-h|--help]
List the SIG's tracking issues per release and package, with the MR each names; with an inventory, the packages missing one
- -i, --inventory <INVENTORY>
sandogasa-inventory TOML; with it every inventory package is classified, `proposed` and `missing` included
- --release <RELEASE>
Restrict to a single release (e.g. `c10s`)
- --package <PACKAGE>
Restrict to these package(s) (repeat/CSV)
- --adopt
Label hand-filed tracking issues `cpu-sig-tracker` without asking, so every command tracks them
- --json
Emit a machine-readable JSON array instead of grouped text
- -v, --verbose
Print progress to stderr
- -h, --help
Print help
cpu-sig-tracker ping
cpu-sig-tracker ping [-i|--inventory] [--release] [--package] [--days] [--reping-days] [-y|--yes] [--dry-run] [--json] [-v|--verbose] [-h|--help]
Nudge upstream merge requests that have gone quiet, and show the last response on those that have not
- -i, --inventory <INVENTORY> [default: inventory.toml]
Path to the sandogasa-inventory TOML file (its workloads name the releases to scan)
- --release <RELEASE>
Restrict the scan to a single release (e.g. `c10s`)
- --package <PKG>
Restrict to these package(s) (repeat/CSV)
- --days <N>
Days without upstream activity before a merge request is pinged (default 14)
- --reping-days <N>
Days after an unanswered ping before it is repeated (default 30)
- -y, --yes
Take the default answer at every prompt without asking, for an unattended run: post each note unless the SIG owes a reply on that change
- --dry-run
Report only: never prompt, never post
- --json
Emit a machine-readable JSON array instead of a table
- -v, --verbose
Print progress to stderr
- -h, --help
Print help
cpu-sig-tracker retire
cpu-sig-tracker retire [--release] [--reason] [--stock-fix] [-y|--yes] [--force] [--claim] [-v|--verbose] [-h|--help] <ISSUE>
Close a tracking issue for a reason — landed, superseded or abandoned — labelling it, telling the MR, closing the MR of an abandoned change
- --release <RELEASE>
With a package name: the release to retire it in (e.g. `c10s`), when it is tracked in several
- --reason <REASON>
Why: landed (the problem is fixed in stock — labelled `superseded` when not by the SIG's own MR) or abandoned (the SIG gives up). Inferred from the MR, stock and the RHEL issue when omitted, and asked at a terminal
Possible values:
- landed: The problem is fixed in stock — by the SIG's MR merging, or another way (labelled `superseded`)
- abandoned: The SIG gives up on the change (Bugzilla's CANTFIX)
- --stock-fix <NVR>
With `--reason landed` and nothing on record: the stock build that carries the fix, as you verified it. Recorded on the issue for `timeline`; asked for at a terminal otherwise
- -y, --yes
Skip the interactive confirmation prompt
- --force
Skip the precondition checks (build untagged, and what the reason needs). Use when the tool can't reach Koji/GitLab or when you're sure the conditions hold
- --claim
Also assign the issue to you as it is closed.
Without this you are asked, unless -y is given: a non-interactive run must not reassign work nobody asked it to.
- -v, --verbose
Print progress to stderr
- -h, --help
Print help (see a summary with '-h')
- <ISSUE>
Tracking issue URL (`/-/issues/<n>` or `/-/work_items/<n>`), or a package name, resolved through the SIG's open tracking issues (`list-issues`)
cpu-sig-tracker status
cpu-sig-tracker status [-i|--inventory] [--release] [-p|--package] [--json] [--refresh] [--include-closed] [-v|--verbose] [-h|--help]
Report JIRA status and suggested next action for each active tracking issue
- -i, --inventory <INVENTORY> [default: inventory.toml]
Path to the sandogasa-inventory TOML file
- --release <RELEASE>
Restrict the check to a single release (e.g. `c10s`)
- -p, --package <PACKAGES>
Narrow to specific packages (repeatable or CSV). When unset, every tracked package in scope is processed. Primarily useful with --refresh to skip the extra work-item-status probes for packages you don't care about
- --json
Emit JSON instead of grouped text
- --refresh
Rewrite tracking issue bodies to the standardized format, refreshing the MR state and JIRA status lines to their current values. Normalizes legacy bodies and keeps already-standard bodies up to date. Mutates GitLab state; off by default
- --include-closed
With --refresh, also process closed tracking issues — backfill their start_date / due_date and reconcile their work-item status against the current JIRA resolution (e.g. Done → Won't do when JIRA was retroactively flipped). Body content is left alone. No-op without --refresh
- -v, --verbose
Print progress to stderr
- -h, --help
Print help
cpu-sig-tracker timeline
cpu-sig-tracker timeline [--release] [--package] [--open-only] [--json] [--csv] [-v|--verbose] [-h|--help]
How long each Proposed Update took and where the time went: filed, covered, fixed in stock, RHEL's advisory, shadowed
- --release <RELEASE>
Restrict to a single release (e.g. `c10s`)
- --package <PACKAGE>
Restrict to these package(s) (repeat/CSV)
- --open-only
Open tracking issues only (closed ones are the history and are included by default)
- --json
Emit a machine-readable JSON array instead of a table
- --csv
Emit CSV with the spreadsheet's columns instead of a table
- -v, --verbose
Print progress to stderr
- -h, --help
Print help
cpu-sig-tracker untag
cpu-sig-tracker untag [-y|--yes] [--force] [-v|--verbose] [-h|--help] <--release> <TARGET>
Untag a proposed_updates build from its CBS -release tag after verifying the JIRA is resolved
- --release <RELEASE>
CentOS release whose proposed_updates tags to untag from (`c9s`, `c10s`, …)
- -y, --yes
Skip the interactive confirmation prompt
- --force
Skip the JIRA-resolved precondition. Use when the tracking issue can't be located or you're sure the check would pass
- -v, --verbose
Print progress to stderr
- -h, --help
Print help
- <TARGET>
Either a package name (e.g. `xz` — the tool discovers the currently-tagged NVR in `-release` and `-testing`) or a specific NVR (e.g. `xz-5.6.4-1~proposed.el10`)