Repository navigation
PG-2843 - OBS QA: Auto Trigger Docker test jobs for ppg:staging 14–18 - #124
Conversation
|
@mohitj1988 I've refactored the project tree structure. The container image packages of The PG components packages that are common to all PG versions have been moved into This PR looks good. Adapt it to the new structure and I'll approve it. |
Adapted the PR to the new changes. Also, created follow-up PRs on ppg-testing and jenkins-pipeline repo. |
Container QA uses the QA team's Docker jobs and ppg-testing main, on the common/ project tree, naming every image by image reference (#133) so PR runs take each image from the PR when the PR built it, else from staging: - ppg:staging:14-18:containers: the server image per UBI base, with and without PostGIS (docker-server-parallel). - ppg:staging:16-18:extras:containers: the custom image (docker-server-parallel-custom). - ppg:staging:common:tools:containers: the pgBackRest and pgBouncer images, each against every major's server image (docker-component-parallel; SERVER_REPOSITORY names it in ppg:staging:<major>:containers). - ppg:staging:common:containers: major upgrades 14->15 ... 17->18 per UBI base, with and without PostGIS (docker-server-parallel-upgrade): mediator from this project, OLD_/NEW_REPOSITORY in their majors' projects. - ppg:staging:common:extras:containers: custom-image upgrades 16->17, 17->18 (docker-server-parallel-custom-upgrade). Replaces docker-server-parallel-generic, the ricardo-work branch and ppg-obs-upgrade. percona-obs: container projects get EXPECTED_VERSIONS from the local projects their repositories build from (subproject: paths, first wins), since their images declare no package version, so the Docker tests check the versions OBS builds. tests: container lanes must be named, unique and cover each UBI base; new tests for the container EXPECTED_VERSIONS.
Per-major container projects (ppg:staging:14-18:containers, shared file):
Extras container projects (ppg:staging:16-18:extras:containers): the custom image (percona-distribution-postgresql-custom) runs on docker-server-parallel-custom; the server-image test ran there before and looked for an image these projects do not build.
The upgrade images (ppg:staging:containers, ppg:staging:extras:containers and the ppg-obs-upgrade entries) are unchanged: their tests pull images from several OBS paths and need per-image repository support first.
tests/test_qa_entry_name.py: container lanes must all be named and include the three UBI lanes, instead of exactly three lanes.