fix(ci): Use Docker-labeled runner for all CI/CD jobs
Some checks failed
Lint and Build / Lint (push) Has been cancelled
Lint and Build / Build (push) Has been cancelled
Lint and Build / Docker Build (push) Has been cancelled

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
This commit is contained in:
goose 2026-02-15 20:41:58 -03:00
parent 775f05d696
commit 04f19e813f
2 changed files with 83 additions and 3 deletions

View file

@ -17,7 +17,7 @@ env:
jobs:
lint:
name: Lint
runs-on: ubuntu-latest
runs-on: docker
steps:
- name: Checkout code
uses: actions/checkout@v4
@ -60,7 +60,7 @@ jobs:
build:
name: Build
runs-on: ubuntu-latest
runs-on: docker
needs: lint
steps:
- name: Checkout code
@ -103,7 +103,7 @@ jobs:
docker-build:
name: Docker Build
runs-on: ubuntu-latest
runs-on: docker
needs: build
steps:
- name: Checkout code

80
FORGEJO-RUNNER-UPDATE.md Normal file
View file

@ -0,0 +1,80 @@
# 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**:
```yaml
jobs:
lint:
runs-on: ubuntu-latest
```
**After**:
```yaml
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:
1. **lint** - `runs-on: docker`
2. **build** - `runs-on: docker`
3. **docker-build** - `runs-on: docker`
---
## Verification
After pushing this change:
1. Go to: http://gitea.soliverez.com.ar/alvaro/normogen/actions
2. Click on the latest workflow run
3. Verify all jobs use the Docker runner
4. Check that jobs complete successfully
---
## Troubleshooting
### If jobs fail with "runner not found":
1. Check runner status in Forgejo admin panel
2. Verify the docker label is configured
3. Check runner is online and unpaused
### If Docker builds fail:
1. Verify Docker is installed on the runner
2. Check runner has sufficient disk space
3. Verify runner can access Docker registry
---
**File Modified**: `.forgejo/workflows/lint-and-build.yml`
**Status**: ✅ Updated & Ready to Push