lab/automation
1
0
Fork 0
Code Issues 6 Pull requests 3 Projects Releases Packages Wiki Activity Actions

Marketplace doc: CI developer guide #12

New issue
Open
opened 2026-09-22 19:42:09 +00:00 by ginjiruu · 0 comments
ginjiruu commented 2026-09-22 19:42:09 +00:00
Owner
Copy link

What to build

The CI developer guide (marketplace doc) in the automation repo, for anyone writing repo-declared CI. Five sections:

  1. The .ci/ convention — folder layout, kustomization, the ci/repo common label, repo-prefixed object names (collision avoidance in the shared ci namespace).
  2. Declaring sensors against the shared bus — the shared webhook subject, the repo-name filter pattern, and that arbitrary event filters are available (tag-only, push-only, comment-triggered, anything the webhook delivers).
  3. Referencing shared templates (go-build-push) vs. writing fully custom workflows in .ci/.
  4. The JSON output-artifact technique — how to surface inspectable build output in the Argo Workflows UI (a JSON output artifact renders in the UI artifact panel). Documented as the convention for marketplace CI developers; not implemented in go-build-push itself.
  5. Link-out to Harbor for image layers/scan.

Acceptance criteria

  • The doc covers all five sections
  • The .ci/ convention described matches the shape proven in the authz-bridge ticket
  • A repo maintainer can onboard CI for a new repo following only the doc + scaffold, without cluster-side help

Blocked by

  • #9 — authz-bridge: first end-to-end (hand-written scaffold + factory entry)
## What to build The CI developer guide (marketplace doc) in the automation repo, for anyone writing repo-declared CI. Five sections: 1. The `.ci/` convention — folder layout, kustomization, the `ci/repo` common label, repo-prefixed object names (collision avoidance in the shared `ci` namespace). 2. Declaring sensors against the shared bus — the shared webhook subject, the repo-name filter pattern, and that arbitrary event filters are available (tag-only, push-only, comment-triggered, anything the webhook delivers). 3. Referencing shared templates (`go-build-push`) vs. writing fully custom workflows in `.ci/`. 4. The JSON output-artifact technique — how to surface inspectable build output in the Argo Workflows UI (a JSON output artifact renders in the UI artifact panel). Documented as the convention for marketplace CI developers; not implemented in `go-build-push` itself. 5. Link-out to Harbor for image layers/scan. ## Acceptance criteria - [ ] The doc covers all five sections - [ ] The `.ci/` convention described matches the shape proven in the authz-bridge ticket - [ ] A repo maintainer can onboard CI for a new repo following only the doc + scaffold, without cluster-side help ## Blocked by - #9 — authz-bridge: first end-to-end (hand-written scaffold + factory entry)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
issue-9-central-allowlist
bridge-moodle-exporter
bridge-ghost-blog
bridge-advent-of-code-2015
bridge-gofantasy
0.0.1
Labels
Clear labels   
ready-for-agent
No labels
ready-for-agent
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
lab/automation#12
No description provided.