Skip to content

Exclude workflow files from yaml lint, since github support none stan… #24

Exclude workflow files from yaml lint, since github support none stan…

Exclude workflow files from yaml lint, since github support none stan… #24

name: Create and publish a Docker image
# Configures this workflow to run on main when testing CI is completed.
on:
workflow_run:
workflows: ["CI"]
branches: [main]
types:
- completed
# Defines two custom environment variables for the workflow. These are used for the Container registry domain, and a name for the Docker image that this workflow builds.
env:
REGISTRY: ghcr.io
IMAGE_NAME: ${{ github.repository }}
CPU: "arm64"
jobs:
on-failure:
runs-on: ubuntu-latest
if: ${{ github.event.workflow_run.conclusion == 'failure' }}
steps:
- run: echo 'The triggering CI workflow failed'
docker-build-and-publish:
runs-on: ubuntu-latest
if: ${{ github.event.workflow_run.conclusion == 'success' }}
# Sets the permissions granted to the `GITHUB_TOKEN` for the actions in this job.
permissions:
contents: read
packages: write
strategy:
matrix:
include:
- context: ./datastore/datastore/
IMAGE_NAME: datastore
CPU: ["arm64", "amd64"]
- context: ./api/
IMAGE_NAME: api
CPU: ["arm64", "amd64"]
# - context: ./ingest/
# IMAGE_NAME: ingest
# CPU: ["arm64", "amd64"]
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Set up QEMU
uses: docker/setup-qemu-action@v3
with:
platforms: ${{ env.CPU }}
- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
# Uses the `docker/login-action` action to log in to the Container registry using the account and password that will publish the packages. Once published, the packages are scoped to the account defined here.
- name: Log in to the Container registry
uses: docker/login-action@v3
with:
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.
- name: Extract metadata (tags, labels) for Docker
id: meta
uses: docker/metadata-action@v5
with:
images: ${{ env.REGISTRY }}/${{ github.repository }}/${{ matrix.IMAGE_NAME }}
tags: |
#Set tag to latest if there is no release tag from git
type=raw,value=latest,enable={{is_default_branch && !tag}}

Check failure on line 71 in .github/workflows/registry_upload.yml

View workflow run for this annotation

GitHub Actions / .github/workflows/registry_upload.yml

Invalid workflow file

You have an error in your yaml syntax on line 71
#Tag the build with the current release
type=tag,event=tag,enable={{is_default_branch}}
- name: Copy Protobuf files to Dockerfile directories
run: ./ci/docker/copy-protobuf.sh
# 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@v5
with:
context: ${{ matrix.context }}
platforms: linux/arm64, linux/amd64
file: ${{ matrix.context }}/Dockerfile
pull: true
push: true
tags: ${{ steps.meta.outputs.tags }}
labels: ${{ steps.meta.outputs.labels }}