All checks were successful
Frontend CI / build (push) Successful in 1m34s
### Description - As the title. ### Package Changes _No response_ ### Screenshots _No response_ ### Reference - Resolves #36 - Solution: https://stackoverflow.com/questions/75131872/error-failed-to-solve-failed-commit-on-ref-unexpected-status-400-bad-reques - Docker document: https://docs.docker.com/build/ci/github-actions/attestations/#max-level-provenance > Note that adding attestations to an image means you must push the image to a registry directly, as opposed to loading the image to the local image store of the runner. This is because the local image store doesn't support loading images with attestations. ### Checklist - [x] A milestone is set - [x] The related issuse has been linked to this branch Reviewed-on: #38 Reviewed-by: zoe <zoe@noreply.localhost> Co-authored-by: SquidSpirit <squid@squidspirit.com> Co-committed-by: SquidSpirit <squid@squidspirit.com>
36 lines
919 B
YAML
36 lines
919 B
YAML
name: Deployment
|
|
on:
|
|
release:
|
|
types:
|
|
- published
|
|
|
|
jobs:
|
|
frontend-deployment:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Checkout
|
|
uses: actions/checkout@v4
|
|
|
|
- name: Set up QEMU
|
|
uses: docker/setup-qemu-action@v3
|
|
|
|
- name: Set up Docker Buildx
|
|
uses: docker/setup-buildx-action@v3
|
|
|
|
- name: Login to registry
|
|
uses: docker/login-action@v3
|
|
with:
|
|
registry: ${{ vars.REGISTRY }}
|
|
username: ${{ vars.REGISTRY_USERNAME }}
|
|
password: ${{ secrets.REGISTRY_PASSWORD }}
|
|
|
|
- name: Build and push
|
|
uses: docker/build-push-action@v6
|
|
with:
|
|
push: true
|
|
provenance: false
|
|
context: ./frontend
|
|
tags: |
|
|
${{ vars.REGISTRY }}/${{ vars.IMAGE_REPO_FRONTEND }}:latest
|
|
${{ vars.REGISTRY }}/${{ vars.IMAGE_REPO_FRONTEND }}:${{ gitea.event.release.tag_name }}
|