04f19e813f
Updated all jobs in the lint-and-build workflow to use the Docker-labeled runner instead of ubuntu-latest. Changes: - lint job: runs-on: docker - build job: runs-on: docker - docker-build job: runs-on: docker Benefits: - Native Docker support - Faster builds - Better performance on local infrastructure - Consistent with server setup
1.6 KiB
1.6 KiB
Forgejo CI/CD Runner Update
Date: 2026-02-15 20:41:00 UTC
Change: Use Docker-labeled runner for all jobs
What Changed
Updated all jobs in the CI/CD pipeline to use the Docker-labeled runner instead of the default ubuntu-latest runner.
Before:
jobs:
lint:
runs-on: ubuntu-latest
After:
jobs:
lint:
runs-on: docker
Why Use the Docker Runner?
Benefits
- ✅ Native Docker support
- ✅ Faster builds (Docker already available)
- ✅ Better performance on your infrastructure
- ✅ Consistent with your server setup
- ✅ Can build Docker images directly
Runner Details
- Label:
docker - Platform: Docker-based
- Available: Yes (configured on your server)
Affected Jobs
All three jobs now use the Docker runner:
- lint -
runs-on: docker - build -
runs-on: docker - docker-build -
runs-on: docker
Verification
After pushing this change:
- Go to: http://gitea.soliverez.com.ar/alvaro/normogen/actions
- Click on the latest workflow run
- Verify all jobs use the Docker runner
- Check that jobs complete successfully
Troubleshooting
If jobs fail with "runner not found":
- Check runner status in Forgejo admin panel
- Verify the docker label is configured
- Check runner is online and unpaused
If Docker builds fail:
- Verify Docker is installed on the runner
- Check runner has sufficient disk space
- Verify runner can access Docker registry
File Modified: .forgejo/workflows/lint-and-build.yml
Status: ✅ Updated & Ready to Push