Skip to content

CI: post-publish sanity check uses a selected target (3.1.x) - #1744

Merged
FelixHelin merged 1 commit into
release/3.1.xfrom
felixhelin-3.1.x-sanity-check-target
Oct 31, 2026
Merged

FelixHelin merged 1 commit into
release/3.1.xfrom
felixhelin-3.1.x-sanity-check-target

Conversation

@FelixHelin

Copy link
Copy Markdown
Contributor

Follow-up to #1741, addressing its Copilot review comment.

The post-publish sanity install was hard-coded to bookworm${SUITE_SUFFIX}/amd64. With targets="focal/amd64 bullseye/armhf" on v3.1.1-rc.1, it would either fail after upload (no bookworm-rc package for 3.1.1) or test a package this run didn't publish.

The plan job now emits a sanity target: bookworm/amd64 when it's selected, so default runs are unchanged; otherwise the first apt-tested selected target (here focal/amd64). The publish job uses that target's codename, arch and base image.

The check always installed bookworm\/amd64, so a targeted
publish (e.g. focal/amd64 bullseye/armhf) would fail after upload when
bookworm-rc is absent, or test an untouched package. The plan job now
emits the sanity target: bookworm/amd64 when selected (default runs are
unchanged), otherwise the first apt-tested target.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Signed-off-by: FelixHelin <felix.dumitrascu@helindata.com>
@FelixHelin
FelixHelin requested a review from helin-ado October 31, 2026 13:58
@FelixHelin
FelixHelin merged commit 28f8edf into release/3.1.x Oct 31, 2026
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants