Codeberg/Community
54
325
Fork
You've already forked Community
12

Issues setting up workflow for codeberg-hosted Forgejo Actions Runner #1718

Closed
opened 2024年11月29日 14:09:24 +01:00 by Andre601 · 1 comment
Contributor
Copy link

Comment

Currently trying to setup a workflow to build and push a page using Codeberg's hosted Forgejo Actions instance (See #1702), but I'm facing annoying problems that I'm unable to solve at all.

My main issue was, and still is, that the actions/setup-python action taken from code.forgejo.org is not working.
Based on what I could gather is the most likely issue an unsupported environement/image, as the action is unable to obtain a proper python version.

Talking in the actions/meta repository here on Codeberg, a suggestion was to add an container image to the workflow, similar to this:

jobsmyJob:runs-on:codeberg-tinycontainer:image:node:22-bookworm

The main issues here are, that I have no idea which image I can/should use here (Are properly supported by the runner).
I tried multiple variations of images here, including:

  • node:22-bookworm: Checkout works but setup-python fails
  • node:23-alpine.19: Checkout fails. Some Git-related issues?
  • ubuntu:20.04: Checkout fails. Missing node instance or smth.
  • alpine:3.20: Checkout fails.

I have a really hard time understanding this setup and the README of actions/meta doesn't really improve on this, as it doesn't answer me the question what image I should use here...

Here is my full workflow file as of most recent commit:

name:Build Wikion:push:branches:- masterpaths:- '.forgejo/workflows/build_wiki.yml'- 'docs/**'- 'domains'- 'mkdocs.yml'- 'requirements.txt'workflow_dispatch:jobs:buildWiki:runs-on:codeberg-tinycontainer:image:node:23-alpine3.19steps:- name:"Checkout Source Repository"uses:https://code.forgejo.org/actions/checkout@v4with:token:"${{ secrets.BOT_TOKEN }}"fetch-depth:0# Prevents issues with git-revision-date-localized plugin- name:"Checkout Target Repository"run:| git clone -b pages https://codeberg.org/Andre601/asl-docs.git site- name:"Setup Python 3.x"uses:https://code.forgejo.org/actions/setup-python@v5with:python-version:3.x- name:"Install dependencies"run:"pip install -r requirements.txt"- name:"Build docs"run:"mkdocs build"- name:"Commit and Push"run:| mv domains site/.domains
 cd site
 git remote set-url origin https://${{ secrets.BOT_TOKEN }}@codeberg.org/Andre601/asl-docs.git
 git add --all
 git commit -m "Update AdvancedServerList Wiki ($( env TZ=Europe/Zurich date +"%d.%m.%Y %Z" ))"
 git push

Workflow runs can be found here: https://codeberg.org/Andre601/AdvancedServerList/actions

I would greatly apreciate it if someone with experience here could provide help in getting this solved.

### Comment Currently trying to setup a workflow to build and push a page using Codeberg's hosted Forgejo Actions instance (See #1702), but I'm facing annoying problems that I'm unable to solve at all. My main issue was, and still is, that the `actions/setup-python` action taken from `code.forgejo.org` is not working. Based on what I could gather is the most likely issue an unsupported environement/image, as the action is unable to obtain a proper python version. Talking in the `actions/meta` repository here on Codeberg, a suggestion was to add an container image to the workflow, similar to this: ```yaml jobs myJob: runs-on: codeberg-tiny container: image: node:22-bookworm ``` The main issues here are, that I have no idea which image I can/should use here (Are properly supported by the runner). I tried multiple variations of images here, including: - `node:22-bookworm`: Checkout works but setup-python fails - `node:23-alpine.19`: Checkout fails. Some Git-related issues? - `ubuntu:20.04`: Checkout fails. Missing node instance or smth. - `alpine:3.20`: Checkout fails. I have a really hard time understanding this setup and the README of `actions/meta` doesn't really improve on this, as it doesn't answer me the question what image I should use here... Here is my full workflow file as of most recent commit: ```yaml name: Build Wiki on: push: branches: - master paths: - '.forgejo/workflows/build_wiki.yml' - 'docs/**' - 'domains' - 'mkdocs.yml' - 'requirements.txt' workflow_dispatch: jobs: buildWiki: runs-on: codeberg-tiny container: image: node:23-alpine3.19 steps: - name: "Checkout Source Repository" uses: https://code.forgejo.org/actions/checkout@v4 with: token: "${{ secrets.BOT_TOKEN }}" fetch-depth: 0 # Prevents issues with git-revision-date-localized plugin - name: "Checkout Target Repository" run: | git clone -b pages https://codeberg.org/Andre601/asl-docs.git site - name: "Setup Python 3.x" uses: https://code.forgejo.org/actions/setup-python@v5 with: python-version: 3.x - name: "Install dependencies" run: "pip install -r requirements.txt" - name: "Build docs" run: "mkdocs build" - name: "Commit and Push" run: | mv domains site/.domains cd site git remote set-url origin https://${{ secrets.BOT_TOKEN }}@codeberg.org/Andre601/asl-docs.git git add --all git commit -m "Update AdvancedServerList Wiki ($( env TZ=Europe/Zurich date +"%d.%m.%Y %Z" ))" git push ``` Workflow runs can be found here: https://codeberg.org/Andre601/AdvancedServerList/actions I would greatly apreciate it if someone with experience here could provide help in getting this solved.
Author
Contributor
Copy link

Resolved by using ghcr.io/catthehacker/ubuntu:act-latest as image.

Resolved by using `ghcr.io/catthehacker/ubuntu:act-latest` as image.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#1718
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?