Repository navigation
PG-2847 - OBS QA: test the PPG tarballs with the QA team's tarball jobs - #137
Merged
Merged
Conversation
ppg:staging:14-18:tarballs (shared file) get a qa: block: one entry per SSL variant repository, each on the tarball job for the platforms with that system OpenSSL: - ssl1.1 -> tarball-parallel-ssl1 (EL8) - ssl3 -> tarball-parallel-ssl3 (EL9/10, Debian 12, Ubuntu 22.04/24.04) - ssl3.5 -> tarball-parallel-ssl35 (Debian 13, Ubuntu 26.04) TARBALL_URL is empty and OBS_PROJECT names this project, so the test takes each host's tarball from the variant's published repository (ppg-testing pg-tarballs). In a PR run OBS_PROJECT is the PR's project, which exists only when the PR rebuilds the tarballs (the image-reference fallback does not cover OBS_PROJECT). A tarballs project has versioned packages of its own (percona-psql), so EXPECTED_VERSIONS listed only those, not the components bundled in the tarball (pgBackRest, Patroni, pgAudit, credcheck, ...), and the tarball tests fell back to the version tables. A project that builds images or tarballs (a package with an obs/Dockerfile, obs/simpleimage or obs/*.kiwi recipe) now also gets the versions of the local projects its repositories build from, after its own: ppg:staging:18:tarballs lists its own percona-psql, then ppg:staging:18's components. Projects without such recipes are unchanged; container projects (no own versions) behave as before. tests: _builds_artifacts and the tarball EXPECTED_VERSIONS; docs updated.
rjd15372
approved these changes
Oct 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ppg:staging:14-18:tarballs (shared file) get a qa: block: one entry per SSL variant repository, each on the tarball job for the platforms with that system OpenSSL:
TARBALL_URL is empty and OBS_PROJECT names this project, so the test takes
each host's tarball from the variant's published repository (ppg-testing
pg-tarballs). In a PR run OBS_PROJECT is the PR's project, which exists only
when the PR rebuilds the tarballs (the image-reference fallback does not
cover OBS_PROJECT).
A tarballs project has versioned packages of its own (percona-psql), so EXPECTED_VERSIONS listed only those, not the components bundled in the tarball (pgBackRest, Patroni, pgAudit, credcheck, ...), and the tarball tests fell back to the version tables.
A project that builds images or tarballs (a package with an obs/Dockerfile, obs/simpleimage or obs/*.kiwi recipe) now also gets the versions of the local projects its repositories build from, after its own: ppg:staging:18:tarballs lists its own percona-psql, then ppg:staging:18's components. Projects without such recipes are unchanged; container projects (no own versions) behave as before.
tests: _builds_artifacts and the tarball EXPECTED_VERSIONS; docs updated.