ci: add pre-verification with registry login test

fix: standardize poimen-workflows CI to unified pattern (#5 )
Unified pattern enforced: - test job: runs on all branches + PRs - build-push job: only on main push, depends on test - Proper env vars (GOPRIVATE, REGISTRY, IMAGE) - Install Node.js before checkout - Install docker only in build-push - Docker login + build + push + prune --------- Co-authored-by: Test <[email protected]> Reviewed-on: #5
2026-09-07 09:00:32 -07:00 · 2026-09-07 07:14:46 +00:00 · 2026-09-07 06:48:25 +00:00 · 2026-09-07 06:23:59 +00:00
1 changed files with 37 additions and 0 deletions
@@ -54,6 +54,43 @@ jobs:
          SHORT_SHA=$(git rev-parse --short HEAD)
          echo "short_sha=${SHORT_SHA}" >> $GITHUB_OUTPUT
      - name: Pre-verify Docker, Registry, and Credentials
        run: |
          echo "=== Docker Daemon Check ==="
          if ! docker version &>/dev/null; then
            echo "❌ FAILED: Docker daemon not accessible"
            exit 1
          fi
          echo "✓ Docker daemon is running"
          docker version --format "Engine: {{.Server.Version}}"
          echo ""
          echo "=== Registry Credentials Check ==="
          if [ -z "${REGISTRY_USER}" ] || [ -z "${REGISTRY_TOKEN}" ]; then
            echo "❌ FAILED: FORGEJO_REGISTRY_USER or FORGEJO_REGISTRY_TOKEN not set"
            exit 1
          fi
          echo "✓ Registry credentials are set"
          echo ""
          echo "=== Registry Login Test ==="
          if ! echo "${REGISTRY_TOKEN}" | docker login "${REGISTRY}" --username "${REGISTRY_USER}" --password-stdin &>/dev/null; then
            echo "❌ FAILED: Registry login failed - credentials may be invalid"
            exit 1
          fi
          echo "✓ Registry login successful"
          docker logout "${REGISTRY}" &>/dev/null || true
          echo ""
          echo "=== Dockerfile Check ==="
          if [ ! -f Dockerfile ]; then
            echo "❌ FAILED: Dockerfile not found"
            exit 1
          fi
          echo "✓ Dockerfile exists"
          echo ""
          echo "=== All pre-checks passed ==="
        env:
          REGISTRY_USER: ${{ secrets.FORGEJO_REGISTRY_USER }}
          REGISTRY_TOKEN: ${{ secrets.FORGEJO_REGISTRY_TOKEN }}
      - name: Registry login
        run: |
          echo "${REGISTRY_TOKEN}" | docker login "${REGISTRY}" \
Author	SHA1	Message	Date
Test	3eb4f4157a	ci: add pre-verification with registry login test CI / Test (pull_request) Successful in 2m20s Details CI / Build & Push Image (pull_request) Skipped Details	2026-09-07 09:00:32 -07:00
rockandTest	70442e94b4	fix: standardize poimen-workflows CI to unified pattern (#5 ) CI / Test (push) Successful in 2m10s Details CI / Build & Push Image (push) Failing after 1m13s Details Unified pattern enforced: - test job: runs on all branches + PRs - build-push job: only on main push, depends on test - Proper env vars (GOPRIVATE, REGISTRY, IMAGE) - Install Node.js before checkout - Install docker only in build-push - Docker login + build + push + prune --------- Co-authored-by: Test <[email protected]> Reviewed-on: #5	2026-09-07 07:14:46 +00:00
rockandTest	45b7f8ca61	fix: use env vars for docker registry credentials (#4 ) CI / Test (push) Successful in 2m7s Details CI / Build & Push Image (push) Failing after 1m5s Details Fix registry login by passing FORGEJO_REGISTRY_USER and FORGEJO_REGISTRY_TOKEN via environment variables instead of direct secret interpolation. Uses the proven pattern from riotpiao.com reference commit. This prevents credentials from being exposed in logs or shell history while keeping the standard docker login approach. After merge + org-level secrets configured: - All repos inherit FORGEJO_REGISTRY_USER and FORGEJO_REGISTRY_TOKEN - CI validates credentials exist before docker login - Image pushed to registry on main push --------- Co-authored-by: Test <[email protected]> Reviewed-on: #4	2026-09-07 06:48:25 +00:00
rockandTest	0261ad141b	fix: separate test and build-push jobs (#3 ) CI / Test (push) Successful in 2m24s Details CI / Build & Push Image (push) Failing after 1m7s Details ## Problem Monolithic test-build-push job runs all steps sequentially, with conditionals for push only on main. This makes it hard to see what failed and doesn't clearly separate concerns. ## Fix Split into two jobs: - test: Runs on all branches + PRs (go mod, vet, test, build binary) - build-push: Runs only on main push after test passes Move env vars to workflow level (cleaner, reused by both jobs). ## Result - PRs: test job runs ✅ (no docker install, no registry push) ✅ - Main push: test → build-push → registry push ✅ --------- Co-authored-by: Test <[email protected]> Reviewed-on: #3	2026-09-07 06:23:59 +00:00