ci: move the container build process to bake #80
Conversation
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
NiccoloFei
force-pushed
the
dev/bake
branch
6 times, most recently
from
c7b9531 to
9f1af55
Compare
NiccoloFei
requested review from
fcanovai,
gbartolini,
litaocdl,
mnencia and
sxd
as code owners
jbattiato
reviewed
May 16, 2025
mnencia
pushed a commit
to cloudnative-pg/cloudnative-pg
that referenced
this pull request
May 19, 2025
…Es (#7303) This patch goes together with cloudnative-pg/postgres-trunk-containers#80. The goal is to allow configuring a custom repository (in this case the `postgresql-trunk`) instead of the default ones (via an env variable), which will be used to fetch the target images required to perform the major upgrade scenarios. This will allow us to test major upgrades to development versions of PG18. Closes #7302 Signed-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com> Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Co-authored-by: Armando Ruocco <armando.ruocco@enterprisedb.com>
cnpg-bot
pushed a commit
to cloudnative-pg/artifacts
that referenced
this pull request
May 20, 2025
…Es (#7303)%0A%0AThis patch goes together with%0Ahttps://github.com/cloudnative-pg/postgres-trunk-containers/pull/80.%0AThe goal is to allow configuring a custom repository (in this case the%0A`postgresql-trunk`) instead of the default ones (via an env variable),%0Awhich will be used to fetch the target images required to perform the%0Amajor upgrade scenarios.%0AThis will allow us to test major upgrades to development versions of%0APG18.%0A%0ACloses #7302%0A%0A%0ASigned-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com>%0ASigned-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com>%0ACo-authored-by: Armando Ruocco <armando.ruocco@enterprisedb.com> cloudnative-pg/cloudnative-pg@refs/heads/main
mnencia
approved these changes
May 20, 2025
cnpg-bot
pushed a commit
to cloudnative-pg/artifacts
that referenced
this pull request
May 21, 2025
…Es (#7303)%0A%0AThis patch goes together with%0Ahttps://github.com/cloudnative-pg/postgres-trunk-containers/pull/80.%0AThe goal is to allow configuring a custom repository (in this case the%0A`postgresql-trunk`) instead of the default ones (via an env variable),%0Awhich will be used to fetch the target images required to perform the%0Amajor upgrade scenarios.%0AThis will allow us to test major upgrades to development versions of%0APG18.%0A%0ACloses #7302%0A%0A%0ASigned-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com>%0ASigned-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com>%0ACo-authored-by: Armando Ruocco <armando.ruocco@enterprisedb.com> cloudnative-pg/cloudnative-pg@refs/heads/main
Signed-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com>
Signed-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com>
Signed-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com>
Signed-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com>
Signed-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com>
Signed-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com>
Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
|
Can we just remove Barman Cloud from the images and disable backup/recovery testing for postgres-trunk? @NiccoloFei Also, can you please update the README as part of this patch? It would be good to show a simple command to run locally to build the image. Thanks. |
Signed-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com>
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.
Switching the build process to bake, creating 3 targets by default: minimal, standard and postgis.
This is an initial effort needed in order to allow running PG Major Upgrade E2E tests also in this repository, which will allow us to test major upgrades to development versions of PG18. The test's are failing at the moment for many reasons, mainly because the target images are not available. See any of the latest CD runs.
In CNPG:
targetImage's repositories that are part of thebuildScenario, allowing us to point to postgresql-trunkNote:
standardtarget, which adds barman-cloud and pgaudit(currently commented out), once plugin-barman-cloud becomes stable