rock/poimen-memory

Fork 0

Files

T

rock c3f5f65540

CI / Test (pull_request) Successful in 2m8s

Details

CI / Build & Push Image (pull_request) Skipped

Details

fix: validate registry credentials before docker login

Problem: Registry login fails silently if secrets aren't configured
- Empty FORGEJO_REGISTRY_USER/TOKEN → docker login hangs/fails
- No clear error message about missing credentials

Solution: Add validation step that checks credentials exist
- Fails early with clear error if secrets missing
- Shows how to configure in repo settings
- Uses direct secret injection (not via env vars)
- Isolates docker config to /tmp/docker-config

Result: CI will fail fast with actionable error if credentials missing

2026-09-06 23:34:48 -07:00

2.3 KiB

Raw Blame History

Forgejo Registry Secrets Configuration

One-Time Setup (Org Level)

All repos in the rock org share the same Forgejo registry credentials.

Configure at Organization Level

Navigate to: https://forgejo.riotpiao.com/rock
Click Settings (gear icon)
Go to: Actions → Secrets
Add these org-level secrets:
- Name: FORGEJO_REGISTRY_USER Value: rock
- Name: FORGEJO_REGISTRY_TOKEN Value: <your-forgejo-token>

Get Your Forgejo Token

Go to: https://forgejo.riotpiao.com/user/settings/applications
Click "Generate New Token"
Set scopes: api, read:registry, write:registry
Copy the token value into the secret

Inheritance

Once org-level secrets are set:

✅ All repos in rock org automatically inherit them
✅ No per-repo configuration needed
✅ Workflows reference via ${{ secrets.FORGEJO_REGISTRY_USER }}

Validation

Each repo's CI workflow includes a validation step:

- name: Validate registry credentials
  run: |
    if [ -z "${{ secrets.FORGEJO_REGISTRY_USER }}" ] || [ -z "${{ secrets.FORGEJO_REGISTRY_TOKEN }}" ]; then
      echo "❌ ERROR: Registry secrets not configured"
      echo "Set FORGEJO_REGISTRY_USER and FORGEJO_REGISTRY_TOKEN in org settings"
      exit 1
    fi
    echo "✓ Registry credentials configured"

If secrets are missing, the validation step will fail with a clear error message pointing to this setup process.

Affected Repositories

The following repos use these shared org-level secrets in their CI workflows:

rock/riotpiao.com
rock/homelab-frontend
rock/poimen-workflows
rock/poimen-memory
rock/kmsvc-manage

All use the unified CI pattern:

test job: runs on all branches + PRs (no registry access)
build-push job: runs on main push only (requires registry credentials)

Troubleshooting

"Registry secrets not configured" error

If CI fails with this error:

Check org settings: https://forgejo.riotpiao.com/rock/settings/actions/secrets
Verify both secrets exist and are not empty
Re-trigger the workflow by pushing to main

If you get error response from daemon: unauthorized:

Check the token value is correct (copy-paste carefully)
Verify token has read:registry and write:registry scopes
Generate a new token if the old one expired

2.3 KiB Raw Blame History