pissing me off
This commit is contained in:
@@ -29,9 +29,11 @@ jobs:
|
||||
username: ${{ gitea.repository_owner }}
|
||||
password: ${{ secrets.GITEATOKEN }}
|
||||
|
||||
- name: Set up QEMU
|
||||
uses: docker/setup-qemu-action@v3
|
||||
|
||||
# QEMU deliberately omitted.
|
||||
#
|
||||
# Hugo runs on BUILDPLATFORM in the Dockerfile, so the static site is
|
||||
# built natively on the runner. The final amd64/arm64 stages only copy
|
||||
# the resulting static files into the target-platform SWS image.
|
||||
- name: Set up Docker Buildx
|
||||
uses: docker/setup-buildx-action@v3
|
||||
|
||||
@@ -46,9 +48,6 @@ jobs:
|
||||
tags: |
|
||||
${{ env.REGISTRY }}/${{ gitea.repository_owner }}/blog-ahmza-com:latest
|
||||
${{ env.REGISTRY }}/${{ gitea.repository_owner }}/blog-ahmza-com:${{ gitea.event.head_commit.id }}
|
||||
# Registry-backed build cache. The GitHub-hosted 'gha' cache is not
|
||||
# reachable from self-hosted Gitea runners, so store the cache as a
|
||||
# dedicated tag in the same registry instead.
|
||||
cache-from: type=registry,ref=${{ env.REGISTRY }}/${{ gitea.repository_owner }}/blog-ahmza-com:buildcache
|
||||
cache-to: type=registry,ref=${{ env.REGISTRY }}/${{ gitea.repository_owner }}/blog-ahmza-com:buildcache,mode=max
|
||||
deploy:
|
||||
@@ -98,11 +97,15 @@ jobs:
|
||||
&& echo "NetBird management connected." \
|
||||
|| { echo "::error title=NetBird not connected::Management not connected after netbird up."; exit 1; }
|
||||
|
||||
- name: Deploy to talos-prod
|
||||
env:
|
||||
KUBE_CONFIG: ${{ secrets.KUBE_CONFIG }}
|
||||
- name: Install Kubectl
|
||||
uses: azure/setup-kubectl@v4
|
||||
with:
|
||||
args: get pods
|
||||
version: v1.36.2
|
||||
|
||||
- name: Deploy to talos-prod
|
||||
env: KUBE_CONFIG: ${{ secrets.KUBE_CONFIG }}
|
||||
run:
|
||||
k get deployment
|
||||
|
||||
- name: NetBird diagnostics & disconnect
|
||||
# Runs even on failure: captures final state for debugging and tears the
|
||||
|
||||
Reference in New Issue
Block a user