Send publish reports to Argus from the release job #17

New issue

Closed

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

Gilles commented

2026-10-30 06:30:11 +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 = <image:tag>|<compressed bytes>|<package page>, the size being the sum of the layers of the linux/amd64 manifest (docker buildx imagetools inspect --raw + jq); /tmp/dependencies.txt = pip freeze inside the pushed image (empty on failure).

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` = `<image:tag>|<compressed bytes>|<package page>`, the size being the sum of the layers of the linux/amd64 manifest (`docker buildx imagetools inspect --raw` + jq); `/tmp/dependencies.txt` = `pip freeze` inside the pushed image (empty on failure).

Gilles referenced this issue from a commit

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

ci: send publish reports to Argus from the release job

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

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

Send publish reports to Argus from the release job #18

Gilles closed this issue

2026-10-30 08:14:21 +00:00

Gilles referenced this issue from a commit

2026-10-30 08:14:22 +00:00

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