Send publish reports to Argus from the release job #5

New issue

Closed

opened 2026-10-30 06:29:30 +00:00 by Gilles · 0 comments

Gilles commented

2026-10-30 06:29:30 +00:00

Owner

Monitoring plan, phase 5 rollout (pilots: argus/backend#45, argus/frontend#35).

publish-release (ci-base) sends a publish report to Argus when ARGUS_UPLOAD_TOKEN is set: version, release page, artifacts with their size, dependencies. Wire it into both release steps (numbered release and devel snapshot).

New step "Collect publish details for Argus": ARGUS_ARTIFACT = built wheel name|bytes|package page; /tmp/dependencies.txt = the runtime dependencies declared in pyproject.toml (name specifier lines, e.g. Django >=4.2).

Monitoring plan, phase 5 rollout (pilots: argus/backend#45, argus/frontend#35). `publish-release` (ci-base) sends a `publish` report to Argus when `ARGUS_UPLOAD_TOKEN` is set: version, release page, artifacts with their size, dependencies. Wire it into both release steps (numbered release and devel snapshot). - New step "Collect publish details for Argus": `ARGUS_ARTIFACT` = built wheel `name|bytes|package page`; `/tmp/dependencies.txt` = the runtime dependencies declared in `pyproject.toml` (`name specifier` lines, e.g. `Django >=4.2`).

Gilles referenced this issue from a pull request that will close it,

2026-10-30 06:29:33 +00:00

Send publish reports to Argus from the release job #6

Gilles referenced this issue from a commit

2026-10-30 06:29:35 +00:00

ci: send publish reports to Argus from the release job

Gilles closed this issue

2026-10-30 08:15:47 +00:00

Gilles referenced this issue from a commit

2026-10-30 08:15:48 +00:00

Send publish reports to Argus from the release job (#6)