fix(ci): split integration tests into separate job#21046
Conversation
Integration tests (registries/scanners/notifiers with `//go:build integration`) hit live external services (quay.io, registry.access.redhat.com) and fail on transient network issues. Running them in the same job as go unit tests means a quay.io timeout fails the entire go unit test job, requiring a full re-run. Move `make integration-unit-tests` to its own `go-integration` job so network flakes can be re-run independently without re-running all unit tests. Partially generated by AI. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Skipping CI for Draft Pull Request. |
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🚀 Build Images ReadyImages are ready for commit ea16053. To use with deploy scripts: export MAIN_IMAGE_TAG=4.12.x-128-gea1605383b |
1 participant
Description
Integration tests (
registries/scanners/notifierspackages with//go:build integration) hit live external services (quay.io, registry.access.redhat.com) and fail on transient network issues. Running them in the same job as go unit tests means a quay.io dial timeout fails the entirego (GOTAGS="")job, requiring a full re-run of all unit tests.Moves
make integration-unit-teststo its owngo-integrationjob so network flakes can be re-run independently.Stacked on #20429 (Gradle 9 test discovery fix).
User-facing documentation
Testing and quality
Automated testing
How I validated my change
The
go-integrationjob is structurally identical to how the step ran before (same checkout, preamble, cache, make target, junit reporting, jira integration). The only difference is isolation: aTestQuaytimeout no longer blocks thegounit test results. Validated YAML syntax withpython3 yaml.safe_load().