Henry
fbd2603883
Some checks failed
Build Docker Linux ARM64 Release / build-docker-linux-arm64-release (push) Failing after 22s
92 lines
3.3 KiB
YAML
92 lines
3.3 KiB
YAML
name: Build Docker Linux ARM64 Release
|
|
run-name: Release-Docker-Linux-ARM64
|
|
|
|
on:
|
|
push:
|
|
branches: [ "main", "master" ]
|
|
|
|
jobs:
|
|
build-docker-linux-arm64-release:
|
|
runs-on: [self-hosted, linux, arm64, docker]
|
|
steps:
|
|
- name: Install packages
|
|
run: apk add --no-cache git curl wget unzip bash nodejs npm docker
|
|
|
|
- name: Clone the repository
|
|
uses: actions/checkout@v4
|
|
with:
|
|
fetch-depth: 0
|
|
|
|
# 1. Nächste Version berechnen
|
|
- name: Determine Next Version
|
|
id: semantic_release
|
|
uses: go-semantic-release/action@v1
|
|
with:
|
|
# Wir übergeben die Gitea-Parameter direkt als Kommandozeilen-Argumente
|
|
custom-arguments: "--provider gitea --gitea-base-url https://gitea.penry.de"
|
|
github-token: ${{ secrets.RELEASE_TOKEN }}
|
|
allow-initial-development-versions: true
|
|
force-bump-patch-version: true
|
|
dry-run: true
|
|
|
|
# 2. Variablen setzen
|
|
- name: Prepare Variables
|
|
run: |
|
|
echo "REPO_LC=${GITHUB_REPOSITORY,,}" >> $GITHUB_ENV
|
|
# WICHTIG: Falls keine neue Version (kein feat/fix), nutzen wir 'latest'
|
|
if [ -z "${{ steps.semantic_release.outputs.version }}" ]; then
|
|
echo "NEXT_VERSION=latest" >> $GITHUB_ENV
|
|
echo "IS_NEW_RELEASE=false" >> $GITHUB_ENV
|
|
else
|
|
echo "NEXT_VERSION=${{ steps.semantic_release.outputs.version }}" >> $GITHUB_ENV
|
|
echo "IS_NEW_RELEASE=true" >> $GITHUB_ENV
|
|
fi
|
|
|
|
- name: Login to own image registry
|
|
uses: docker/login-action@v3
|
|
with:
|
|
registry: gitea.penry.de
|
|
username: ${{ secrets.REGISTRY_USER }}
|
|
password: ${{ secrets.REGISTRY_PASSWORD }}
|
|
|
|
- name: Setup .NET10
|
|
uses: actions/setup-dotnet@v3
|
|
with:
|
|
dotnet-version: '10.0.x'
|
|
|
|
# 3. Build & Push
|
|
- name: Build and Push Docker Image
|
|
run: |
|
|
# Wir bauen immer latest
|
|
TAGS="-t gitea.penry.de/${{ env.REPO_LC }}:latest"
|
|
# Wenn eine neue SemVer Version da ist, fügen wir diesen Tag hinzu
|
|
if [ "${{ env.IS_NEW_RELEASE }}" = "true" ]; then
|
|
TAGS="$TAGS -t gitea.penry.de/${{ env.REPO_LC }}:${{ env.NEXT_VERSION }}"
|
|
fi
|
|
|
|
docker build $TAGS \
|
|
--label "org.opencontainers.image.source=https://gitea.penry.de/${{ github.repository }}" \
|
|
.
|
|
|
|
docker push gitea.penry.de/${{ env.REPO_LC }} --all-tags
|
|
|
|
# 4. Git Tag & Release in Gitea erstellen (Falls neue Version vorhanden)
|
|
- name: Execute Semantic Release
|
|
if: env.IS_NEW_RELEASE == 'true'
|
|
uses: go-semantic-release/action@v1
|
|
with:
|
|
custom-arguments: "--provider gitea --gitea-base-url https://gitea.penry.de"
|
|
github-token: ${{ secrets.RELEASE_TOKEN }}
|
|
|
|
# 5. Tar Export & Gitea Release Asset
|
|
- name: Export Image Tar
|
|
if: env.IS_NEW_RELEASE == 'true'
|
|
run: |
|
|
docker save -o couchlog-linux-arm64-${{ env.NEXT_VERSION }}.tar gitea.penry.de/${{ env.REPO_LC }}:${{ env.NEXT_VERSION }}
|
|
|
|
- name: Upload Release Asset
|
|
if: env.IS_NEW_RELEASE == 'true'
|
|
uses: akkuman/gitea-release-action@v1
|
|
with:
|
|
files: |-
|
|
couchlog-linux-arm64-${{ env.NEXT_VERSION }}.tar |