Skip to content

Conversation

@cpuguy83
Copy link
Collaborator

@cpuguy83 cpuguy83 commented Jan 7, 2026

This causes CI time to blow up because in CI we split builds so that each distro is built in a separate job, however with the test the way it was before we ended up having to do additional work to build 2 other distros which takes up a bunch of extra time (fetch the images, prepare worker image) and space.

The change, instead of building each target, now just builds the primary and asserts that none of the other distro's artifacts are in it.

Closes #903

This causes CI time to blow up because in CI we split builds so that
each distro is built in a separate job, however with the test the way it
was before we ended up having to do additional work to build 2 other
distros which takes up a bunch of extra time (fetch the images, prepare
worker image) and space.

The change, instead of building each target, now just builds the primary
and asserts that none of the other distro's artifacts are in it.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>
Copilot AI review requested due to automatic review settings January 7, 2026 22:15
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR optimizes the multi-artifact test to reduce CI build time by eliminating redundant distro builds. Instead of building all three distros (primary, secondary, and tertiary targets) to verify that target-level artifacts take precedence, the test now only builds the primary target and uses negative assertions (NotExist checks) to verify that artifacts from other targets are correctly excluded.

Key Changes

  • Removed separate test runs for secondary and tertiary targets, reducing from 3 builds to 1 build per distro
  • Modified artifact naming to use target-specific names (e.g., "from-mariner2") instead of generic names
  • Added NotExist assertions for secondary, tertiary, and main artifacts to verify proper artifact precedence without building those targets

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.

[BUG] testTargetArtifactsTakePrecedence tests too much

1 participant