From c4642a1da5051fc49ebedca1bc6333873e25f908 Mon Sep 17 00:00:00 2001 From: Benedikt Heine Date: Sun, 3 Mar 2024 19:34:47 +0100 Subject: [PATCH] Testing main workflow; now with matrix from main project --- .github/workflows/main.yml | 24 ++++++++++++++++++------ 1 file changed, 18 insertions(+), 6 deletions(-) diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index 8aef053..ce39938 100644 --- a/.github/workflows/main.yml +++ b/.github/workflows/main.yml @@ -14,6 +14,17 @@ env: # There is a single job in this workflow. It's configured to run on the latest available version of Ubuntu. jobs: build-and-push-image: + strategy: + matrix: + distro: + - alpine + - archlinux + - debian-stretch + - debian-buster + - fedora + - ubuntu-xenial + - ubuntu-bionic + - ubuntu-focal runs-on: ubuntu-latest # Sets the permissions granted to the `GITHUB_TOKEN` for the actions in this job. permissions: @@ -30,20 +41,21 @@ jobs: registry: ${{ env.REGISTRY }} username: ${{ github.actor }} password: ${{ secrets.GITHUB_TOKEN }} - # This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) to extract tags and labels that will be applied to the specified image. The `id` "meta" allows the output of this step to be referenced in a subsequent step. The `images` value provides the base name for the tags and labels. + + # Default metadata action step. + # Will add some "org.opencontainers.*"-labels with useful descriptions + # However the tags are totally unusable for our case - name: Extract metadata (tags, labels) for Docker id: meta uses: docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7 with: images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }} - # This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages. - # It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the `docker/build-push-action` repository. - # It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step. + - name: Build and push Docker image uses: docker/build-push-action@f2a1d5e99d037542a71f64918e516c093c6f3fc4 with: context: ci - file: ci/Dockerfile.alpine + file: ci/Dockerfile.${{ matrix.distro }} push: true - tags: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}/alpine + tags: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:${{ matrix.distro }} labels: ${{ steps.meta.outputs.labels }}