c92d845639
Refactor the workflows so that we can use build-push-action also for publishing. This is a precondition for switching to buildx, needed for multi-arch images. The trick needed for this is using an environment variable to control whether we should push when building the master branch, initializing it according to the tag status. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
40 lines
1.1 KiB
YAML
40 lines
1.1 KiB
YAML
name: release
|
|
|
|
on:
|
|
push:
|
|
tags:
|
|
- '*.*'
|
|
|
|
jobs:
|
|
deploy_containers:
|
|
name: Build and deploy container images
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Check out repo
|
|
uses: actions/checkout@v2
|
|
- name: Get release
|
|
run: echo "RELEASE_VERSION=${GITHUB_REF#refs/tags/}" >> $GITHUB_ENV
|
|
- name: Login to ghcr.io
|
|
uses: docker/login-action@v1
|
|
with:
|
|
registry: ghcr.io
|
|
username: ${{ secrets.PACKAGE_DEPLOY_USER }}
|
|
password: ${{ secrets.PACKAGE_DEPLOY_TOKEN }}
|
|
- name: Build kas image
|
|
uses: docker/build-push-action@v2
|
|
with:
|
|
push: true
|
|
tags: |
|
|
ghcr.io/siemens/kas/kas
|
|
ghcr.io/siemens/kas/kas:${{ env.RELEASE_VERSION }}
|
|
ghcr.io/siemens/kas/kas:latest-release
|
|
- name: Build kas-isar image
|
|
uses: docker/build-push-action@v2
|
|
with:
|
|
file: Dockerfile.isar
|
|
push: true
|
|
tags: |
|
|
ghcr.io/siemens/kas/kas-isar
|
|
ghcr.io/siemens/kas/kas-isar:${{ env.RELEASE_VERSION }}
|
|
ghcr.io/siemens/kas/kas-isar:latest-release
|