vicoli-oss/docker-forgejo-mcp
Watch
1
0
Fork
You've already forked docker-forgejo-mcp
 0
Code Issues Pull requests Projects Releases Packages 1 Activity Actions

CI builds and smoke-tests the Image on every PR #6

New issue
Closed
opened 2026-09-30 13:14:53 +00:00 by piscis · 1 comment
piscis commented 2026-09-30 13:14:53 +00:00
Owner
Copy link

What to build

A PR workflow on the docker runner that builds the Image for linux/amd64 and linux/arm64 from the Pin and runs the smoke test against each architecture. It reuses the build and smoke-test commands from the local tracer bullet rather than duplicating their logic. It never pushes to the registry.

Use whatever the runner probe established as the working way to reach Docker and emulate arm64.

Acceptance criteria

  • Opening or updating a PR triggers the workflow, which builds both architectures and runs the smoke test on both
  • A PR with a broken Dockerfile turns red
  • A PR whose Pin commit doesn't match the Upstream tag turns red
  • Nothing is pushed to code.vicoli.de from a PR run
  • The workflow can also be dispatched manually

Blocked by

Context: see GLOSSARY.md (Upstream, Upstream Version, Image, Rebuild, Consumer, Pin) and docs/adr/ (0001 build from Upstream source for multi-arch, 0002 canonical Upstream not the Codeberg mirror, 0003 tag scheme and immutable Rebuild tags).

## What to build A PR workflow on the `docker` runner that builds the Image for linux/amd64 and linux/arm64 from the Pin and runs the smoke test against each architecture. It reuses the build and smoke-test commands from the local tracer bullet rather than duplicating their logic. It never pushes to the registry. Use whatever the runner probe established as the working way to reach Docker and emulate arm64. ## Acceptance criteria - [x] Opening or updating a PR triggers the workflow, which builds both architectures and runs the smoke test on both - [x] A PR with a broken Dockerfile turns red - [x] A PR whose Pin commit doesn't match the Upstream tag turns red - [x] Nothing is pushed to `code.vicoli.de` from a PR run - [x] The workflow can also be dispatched manually ## Blocked by - #3 - #4 Context: see `GLOSSARY.md` (Upstream, Upstream Version, Image, Rebuild, Consumer, Pin) and `docs/adr/` (0001 build from Upstream source for multi-arch, 0002 canonical Upstream not the Codeberg mirror, 0003 tag scheme and immutable Rebuild tags).
piscis self-assigned this 2026-09-30 14:26:15 +00:00
piscis 2026-09-30 14:34:20 +00:00
piscis commented 2026-09-30 15:15:18 +00:00
Author
Owner
Copy link

Done. ci (.forgejo/workflows/ci.yml) builds and smoke-tests the Image for amd64 and arm64 on every PR and on manual dispatch. It landed in #20, with follow-ups #23 and #24.

Acceptance criterion Evidence
PR triggers build and smoke test of both architectures PR runs 4, 9, 21, 25: green, PASS: 156 tools listed on amd64 and arm64
Broken Dockerfile turns red run 5, throwaway commit, reverted
Pin commit ≠ Upstream tag turns red run 6: Upstream tag v3.2.0 resolves to commit e30bb7e…, but the Pin expects 0000…, throwaway commit, reverted
Nothing pushed to code.vicoli.de no docker login, no --push, no secrets, --load only; the checkout token is removed right after the fetch (#23); GET /api/v1/packages/vicoli-oss?type=container returns []
Manual dispatch e.g. run 28 on main after #24, green

Along the way:

  • Runner DNS (#22, closed): RUN steps on the runner's dind daemon couldn't resolve names, because the runner's firewall blocked outbound DNS (UDP port 53). #23 worked around it with --network host. The firewall is now fixed, and #24 removed the workaround.
  • Shared daemon: concurrent runs don't collide. Image tags are per run, and smoke-test container and network names are random per run. The PR run plus two concurrent dispatches on the same commit, with a cold cache, were all green (25, 26, 27).
  • tonistiigi/binfmt is pinned by digest (#23).

Left open, outside this issue's criteria: #25. A cached clone step can hide an Upstream tag that moves without a Pin change.

Done. `ci` (`.forgejo/workflows/ci.yml`) builds and smoke-tests the Image for amd64 and arm64 on every PR and on manual dispatch. It landed in #20, with follow-ups #23 and #24. | Acceptance criterion | Evidence | |---|---| | PR triggers build and smoke test of both architectures | PR runs [4](https://code.vicoli.de/vicoli-oss/docker-forgejo-mcp/actions/runs/4), [9](https://code.vicoli.de/vicoli-oss/docker-forgejo-mcp/actions/runs/9), [21](https://code.vicoli.de/vicoli-oss/docker-forgejo-mcp/actions/runs/21), [25](https://code.vicoli.de/vicoli-oss/docker-forgejo-mcp/actions/runs/25): green, `PASS: 156 tools listed` on amd64 and arm64 | | Broken Dockerfile turns red | [run 5](https://code.vicoli.de/vicoli-oss/docker-forgejo-mcp/actions/runs/5), throwaway commit, reverted | | Pin commit ≠ Upstream tag turns red | [run 6](https://code.vicoli.de/vicoli-oss/docker-forgejo-mcp/actions/runs/6): `Upstream tag v3.2.0 resolves to commit e30bb7e…, but the Pin expects 0000…`, throwaway commit, reverted | | Nothing pushed to `code.vicoli.de` | no `docker login`, no `--push`, no secrets, `--load` only; the checkout token is removed right after the fetch (#23); `GET /api/v1/packages/vicoli-oss?type=container` returns `[]` | | Manual dispatch | e.g. [run 28](https://code.vicoli.de/vicoli-oss/docker-forgejo-mcp/actions/runs/28) on main after #24, green | Along the way: - **Runner DNS (#22, closed):** `RUN` steps on the runner's dind daemon couldn't resolve names, because the runner's firewall blocked outbound DNS (UDP port 53). #23 worked around it with `--network host`. The firewall is now fixed, and #24 removed the workaround. - **Shared daemon:** concurrent runs don't collide. Image tags are per run, and smoke-test container and network names are random per run. The PR run plus two concurrent dispatches on the same commit, with a cold cache, were all green ([25](https://code.vicoli.de/vicoli-oss/docker-forgejo-mcp/actions/runs/25), [26](https://code.vicoli.de/vicoli-oss/docker-forgejo-mcp/actions/runs/26), [27](https://code.vicoli.de/vicoli-oss/docker-forgejo-mcp/actions/runs/27)). - **`tonistiigi/binfmt`** is pinned by digest (#23). Left open, outside this issue's criteria: #25. A cached clone step can hide an Upstream tag that moves without a Pin change.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
piscis/32-claude-setup-update
piscis/forgejo-issue-8-implement
piscis/forgejo-16-implement
piscis/vicoli-oss-descriptions-add
piscis/forgejo-4-multi-arch-implement
piscis/forgejo-mcp-docker-image-plan
piscis/matt-pocock-skills-setup
piscis/mcp.json-context7-config
No results found.
Labels
Clear labels   
bug
Something is broken

  
enhancement
New feature or improvement

  
needs-info
Waiting on reporter for more information

  
needs-triage
Maintainer needs to evaluate this issue

  
ready-for-agent
Fully specified, ready for an AFK agent

  
ready-for-human
Requires human implementation

  
wayfinder:grilling
Wayfinder ticket: grilling

  
wayfinder:map
Wayfinder map: Notes / Decisions-so-far / Fog

  
wayfinder:prototype
Wayfinder ticket: prototype

  
wayfinder:research
Wayfinder ticket: research

  
wayfinder:task
Wayfinder ticket: task

  
wontfix
Will not be actioned

No labels
bug
enhancement
needs-info
needs-triage
ready-for-agent
ready-for-human
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
piscis
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.

Blocks
#7 Publish the Image on push to main
vicoli-oss/docker-forgejo-mcp
#8 Renovate opens bump PRs for new Upstream Versions
vicoli-oss/docker-forgejo-mcp
Depends on
#3 Probe the runner's Docker and buildx capabilities
vicoli-oss/docker-forgejo-mcp
#4 Build a multi-arch Image from the Pin and smoke-test it locally
vicoli-oss/docker-forgejo-mcp
Reference
vicoli-oss/docker-forgejo-mcp#6
No description provided.