-
nimrod authored
Those jobs are not always in the workflow and that makes the workflow invalid in those cases. Since the build and push already happens before those jobs will use the newer base images anyway.
nimrod authoredThose jobs are not always in the workflow and that makes the workflow invalid in those cases. Since the build and push already happens before those jobs will use the newer base images anyway.
.gitlab-ci.yml 2.58 KiB
---
include:
- project: shore/ci-stuff
file: templates/pre-commit.yml
- project: shore/ci-stuff
file: templates/notify.yml
- project: shore/ci-stuff
file: templates/containerfiles.yml
# Base image templates:
stages:
- build-base
- deploy-base
- build
- deploy
.container-build-base:
extends: .container-build
stage: build-base
.container-push-base:
extends: .container-push
stage: deploy-base
# cgit image:
build-cgit:
extends: .container-build
variables:
CONTEXT: cgit
push-cgit:
extends: .container-push
variables:
CONTEXT: cgit
IMAGE: cgit
needs:
- job: build-cgit
artifacts: true
# httpd latest image:
build-httpd:
extends: .container-build-base
variables:
CONTEXT: httpd/bullseye
push-httpd:
extends: .container-push-base
variables:
CONTEXT: httpd/bullseye
IMAGE: httpd
needs:
- job: build-httpd
artifacts: true
# httpd bullseye image:
push-httpd-bullseye:
extends: .container-push-base
variables:
CONTEXT: httpd/bullseye
IMAGE: httpd
TAG: bullseye
needs:
- job: build-httpd
artifacts: true
# httpd buster image: