# 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