June
2906ee45d8
organize the image publishing/tagging process better
...
ci/woodpecker/push/keycloak Pipeline was successful
ci/woodpecker/push/nextcloud/2 Pipeline was successful
ci/woodpecker/push/nextcloud/1 Pipeline was successful
Every image gets pushed with a unique version-branch tag by default and
then the version and latest tags get only tagged from the main branch
and the main branch and the desired version respectively.
2024-08-10 19:16:52 +02:00
christian
69c5ef00fe
only tag branch & latest if version equals check
ci/woodpecker/push/keycloak Pipeline was successful
ci/woodpecker/push/nextcloud/2 Pipeline was successful
ci/woodpecker/push/nextcloud/1 Pipeline was successful
2024-07-28 00:02:40 +02:00
christian
14df00e631
Fix: push images with the version tag first
ci/woodpecker/push/keycloak Pipeline was successful
ci/woodpecker/push/nextcloud/1 Pipeline was successful
ci/woodpecker/push/nextcloud/2 Pipeline was successful
2024-07-27 23:27:23 +02:00
christian
4fcbc46175
Build Container on push if it's files have changed
ci/woodpecker/push/nextcloud/1 Pipeline failed
ci/woodpecker/push/nextcloud/2 Pipeline failed
ci/woodpecker/push/keycloak Pipeline was successful
2024-07-27 23:19:14 +02:00
June
bc8cd3dec6
Only tag with branch name everytime and tag with ver. and latest on main
...
ci/woodpecker/push/keycloak Pipeline was successful
This way the version tag is stable aka only points to builds from main.
2024-07-27 01:33:46 +02:00
June
00158d0205
setup automated Keycloak image builds with Woodpecker, kaniko and crane
...
ci/woodpecker/push/keycloak Pipeline was successful
This way the Keycloak host can simply pull a finished image and doesn't
need to build a Keycloak image itself.
Co-authored-by: c6ristian <c6ristian@christian.moe>
2024-07-27 01:16:31 +02:00
June
christian