toolshed/coop-cloud-backend
3
4
Fork 2
Code Issues Pull Requests 1 Actions Packages Releases Activity

Building #3

Merged
sixsmith merged 9 commits from building into main 2026-08-27 11:36:21 +00:00
Conversation 3 Commits 9 Files Changed 2
+97
2 changed files with 97 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/build.yaml
+44
View File
@@ -0,0 +1,44 @@
name: Build And Publish Container
on:
push:
branches:
- '*'
jobs:
build-latest:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
with:
submodules: 'recursive'
fetch-depth: 0
- name: Get short commit SHA
id: vars
run: |
calculatedSha=$(git rev-parse --short ${{ github.sha }})
sixsmith marked this conversation as resolved
sixsmith commented 2026-08-21 16:06:32 +00:00
Review
Copy Link
Copy Source

Is github.sha supposed to be available in this context?

Is `github.sha` supposed to be available in this context?
echo "COMMIT_SHORT_SHA=$calculatedSha" >> $GITHUB_ENV
- name: Set up Docker Buildx
id: buildx
uses: docker/setup-buildx-action@bb05f3f5519dd87d3ba754cc423b652a5edd6d2c # v4.2.0
with:
platforms: linux/amd64
- name: Login to Self-Hosted Registry
uses: docker/login-action@af1e73f918a031802d376d3c8bbc3fe56130a9b0 # v4.4.0
with:
registry: git.coopcloud.tech
username: ${{ secrets.REGISTRY_USER }}
password: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
- name: Build and Push
uses: docker/build-push-action@53b7df96c91f9c12dcc8a07bcb9ccacbed38856a # v7.3.0
with:
builder: ${{ steps.buildx.outputs.name }}
context: ./
file: ./Dockerfile
platforms: linux/amd64
push: true
tags: git.coopcloud.tech/toolshed/coop-cloud-webui:nightly-${{ env.COMMIT_SHORT_SHA }}
.gitea/workflows/tag-build.yaml
+53
View File
@@ -0,0 +1,53 @@
name: Build And Publish Container
on:
push:
tags:
- "[0-9]*.[0-9]*.[0-9]*"
workflow_dispatch:
inputs:
tag:
description: "Version tag (e.g., 0.1.0)"
required: true
jobs:
build-latest:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
with:
submodules: 'recursive'
fetch-depth: 0
- name: Get release tag
id: vars
run: |
if [ "${{ gitea.event_name }}" = "workflow_dispatch" ]; then
TAG="${{ gitea.inputs.version }}"
else
TAG="${{ gitea.ref_name }}"
fi
echo "RELEASE_TAG=$TAG" >> $GITHUB_ENV
sixsmith marked this conversation as resolved
sixsmith commented 2026-08-21 16:07:11 +00:00
Review
Copy Link
Copy Source

Same here as above, is $GITHUB_ENV going to set env.RELEASE_TAG in a non-GitHub context?

Same here as above, is `$GITHUB_ENV` going to set `env.RELEASE_TAG` in a non-GitHub context?
Brooke commented 2026-08-25 18:43:26 +00:00
Review
Copy Link
Copy Source

My understanding is that the act runner we're using is built for supporting github actions first and gitea/forgejo add variables on top. So, it has worked in testing on local and remote runners.

My understanding is that the act runner we're using is built for supporting github actions first and gitea/forgejo add variables on top. So, it has worked in testing on local and remote runners.
- name: Set up Docker Buildx
id: buildx
uses: docker/setup-buildx-action@bb05f3f5519dd87d3ba754cc423b652a5edd6d2c # v4.2.0
with:
platforms: linux/amd64
- name: Login to Self-Hosted Registry
uses: docker/login-action@af1e73f918a031802d376d3c8bbc3fe56130a9b0 # v4.4.0
with:
registry: git.coopcloud.tech
username: ${{ secrets.REGISTRY_USER }}
password: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
- name: Build and Push
uses: docker/build-push-action@53b7df96c91f9c12dcc8a07bcb9ccacbed38856a # v7.3.0
with:
builder: ${{ steps.buildx.outputs.name }}
context: ./
file: ./Dockerfile
platforms: linux/amd64
push: true
tags: git.coopcloud.tech/toolshed/coop-cloud-webui:${{ env.RELEASE_TAG }}