forgejo_admin/minio-api
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

Onboard minio-api to Woodpecker CI pipeline #8

New issue
Open
opened 2026-03-28 18:08:15 +00:00 by forgejo_admin · 0 comments
forgejo_admin commented 2026-03-28 18:08:15 +00:00
Owner
Copy link

Type

Feature

Lineage

  • Discovered scope from pal-e-platform #206 — kustomize-tag rollout blocked on Woodpecker onboarding
  • Board: board-pal-e-platform
  • Story: story:superuser-deploy
  • Arch: arch:ci-pipeline

Repo

forgejo_admin/minio-api

User Story

As a platform operator, I want minio-api in Woodpecker CI so that merges trigger automated builds, image pushes, and kustomize tag updates — completing the GitOps pipeline for this service.

Context

minio-api is a FastAPI REST service wrapping minio-sdk (27 tests). It currently has no CI pipeline. The kustomize-tag rollout (pal-e-platform #206) is blocked until this repo is onboarded to Woodpecker.

Scope

  1. Activate repo in Woodpecker
  2. Create .woodpecker.yaml pipeline (test, build, push to Harbor, update-kustomize-tag step)
  3. Provision required secrets (forgejo_token, Harbor registry creds)
  4. Verify one successful end-to-end pipeline run

File Targets

  • .woodpecker.yaml (new)

Acceptance Criteria

  • Repo activated in Woodpecker CI
  • .woodpecker.yaml with test + build + push + update-kustomize-tag steps
  • forgejo_token secret provisioned
  • Harbor registry credentials provisioned
  • One successful pipeline run (push → test → build → push → tag update)

Test Expectations

  • Push a trivial change, verify full pipeline runs green
  • Verify all 27 existing tests pass in CI
  • Verify kustomize overlay tag updates in pal-e-deployments
  • Run: kubectl get application minio-api -n argocd to verify ArgoCD sync

Constraints

  • Follow existing pipeline patterns from pal-e-api or basketball-api
  • Use scripts/update-kustomize-tag.sh from pal-e-platform
  • minio-api has 27 tests — pipeline must run them

Checklist

  • Activate repo in Woodpecker admin
  • Create .woodpecker.yaml
  • Add forgejo_token secret
  • Add Harbor registry secrets
  • Run first pipeline
  • Verify tests pass in CI
  • Verify end-to-end

Related

  • forgejo_admin/pal-e-platform#206 — parent rollout issue
  • forgejo_admin/pal-e-platform#205 — reusable script PR
  • forgejo_admin/basketball-api#192 — reference implementation
### Type Feature ### Lineage - Discovered scope from pal-e-platform #206 — kustomize-tag rollout blocked on Woodpecker onboarding - Board: board-pal-e-platform - Story: story:superuser-deploy - Arch: arch:ci-pipeline ### Repo `forgejo_admin/minio-api` ### User Story As a platform operator, I want minio-api in Woodpecker CI so that merges trigger automated builds, image pushes, and kustomize tag updates — completing the GitOps pipeline for this service. ### Context minio-api is a FastAPI REST service wrapping minio-sdk (27 tests). It currently has no CI pipeline. The kustomize-tag rollout (pal-e-platform #206) is blocked until this repo is onboarded to Woodpecker. ### Scope 1. Activate repo in Woodpecker 2. Create `.woodpecker.yaml` pipeline (test, build, push to Harbor, update-kustomize-tag step) 3. Provision required secrets (`forgejo_token`, Harbor registry creds) 4. Verify one successful end-to-end pipeline run ### File Targets - `.woodpecker.yaml` (new) ### Acceptance Criteria - [ ] Repo activated in Woodpecker CI - [ ] `.woodpecker.yaml` with test + build + push + update-kustomize-tag steps - [ ] `forgejo_token` secret provisioned - [ ] Harbor registry credentials provisioned - [ ] One successful pipeline run (push → test → build → push → tag update) ### Test Expectations - [ ] Push a trivial change, verify full pipeline runs green - [ ] Verify all 27 existing tests pass in CI - [ ] Verify kustomize overlay tag updates in pal-e-deployments - Run: `kubectl get application minio-api -n argocd` to verify ArgoCD sync ### Constraints - Follow existing pipeline patterns from pal-e-api or basketball-api - Use `scripts/update-kustomize-tag.sh` from pal-e-platform - minio-api has 27 tests — pipeline must run them ### Checklist - [ ] Activate repo in Woodpecker admin - [ ] Create `.woodpecker.yaml` - [ ] Add `forgejo_token` secret - [ ] Add Harbor registry secrets - [ ] Run first pipeline - [ ] Verify tests pass in CI - [ ] Verify end-to-end ### Related - `forgejo_admin/pal-e-platform#206` — parent rollout issue - `forgejo_admin/pal-e-platform#205` — reusable script PR - `forgejo_admin/basketball-api#192` — reference implementation
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo_admin/minio-api#8
No description provided.