Files

T

ci/woodpecker/tag/docker Pipeline was successful

Details

npm clients need one registry for internal and public packages, but npm virtuals have no merger, so a local npm repo and npmjs cannot be served together.

- merge packuments across members: union versions (member order wins), first-defined dist-tags minus ones naming missing versions
- serve full and abbreviated (`install-v1`) packuments, scoped names included, via the shared virtual merge cache
- point tarballs at `<virtual>/<member>/<path>` and 302 them to the owning member
- reject an invalid Host with 400; serve virtual and local packuments `no-store` with `Vary: Host, X-Forwarded-Proto, Accept`
- return 502 when a member errors; skip members without the package
- add `docs/npm/virtual.md` and a stock `node:22` e2e-docker case

Reviewed-on: #152
Co-authored-by: unkin-agent <unkin-agent@unkin.net>
Co-committed-by: unkin-agent <unkin-agent@unkin.net>

2026-10-17 21:52:55 +11:00

2.9 KiB

Raw Blame History

Dockerised end-to-end suite

Black-box tests that run against a fully containerised artifactapi stack (built image + Postgres + Redis + MinIO) plus a static mock upstream. Unlike the in-process e2e/ suite (testcontainers, server run in-process), these only speak HTTP to the running product, so they exercise the shipped container image.

Run

make docker-e2e          # build image, compose up, run suite, compose down

scripts/docker-e2e.sh builds and starts docker-compose.yml + docker-compose.e2e.yml, waits for /health, then runs go test -tags=dockere2e ./e2e-docker/... and tears everything down.

The stack publishes artifactapi on host port 8001 (to avoid colliding with a local instance on 8000). Override with ARTIFACTAPI_URL to point the tests at an already-running stack.

Coverage

Repository lifecycle — add / change / delete for remote, local and virtual repos.
Caching — one immutable artifact per remote package type (one caching_<type>_test.go case each) proxied through the mock upstream: first fetch X-Artifact-Source: remote, second cache, bytes verified against the origin fixture.
Local uploads — puppet (Forge v3 API via real r10k and puppet module install), generic (upload/download), pypi (wheel + generated simple/ index), rpm (real package + automatic repodata generation), npm (stock node:22 client: npm publish unscoped + scoped, npm install + require(), second version, republish rejected).
Virtual repositories — pypi simple-index merge and helm index.yaml merge across two members; npm packument merge over two locals via a stock node:22 client (merged versions, install through the member redirect).
Mirrorlist — an rpm remote with a mirrorlist of extra upstream mirrors (pool = base_url + mirrorlist): round-robin distribution across both mirrors (constant-body mockupstreama / mockupstreamb), failover past a dead primary, no-mirrorlist regression, and a real dnf (stock rockylinux:9 container) makecache + install through a two-mirror rpm remote whose base_url is dead — a dead mirror must not break the client.
Mirror strategy (least_conn) — a mirror_strategy: least_conn rpm remote over the two constant-body mirrors exercises the least-connections selection path end-to-end (both mirrors serve, all requests succeed), plus a real dnf install through a least_conn remote with a dead primary (failover unchanged). The precise least-loaded pick is asserted deterministically in the proxy unit test, since an in-flight-skew assertion over HTTP is timing-sensitive.

Fixtures

fixtures/ is served by the mock upstream at its web root. Paths mirror each provider's upstream URL layout (e.g. v2/... for docker, v1/providers/... for terraform). The RPM under fixtures/rpmrepo/Packages/ is a real package so the rpm provider can parse its metadata for repodata generation.

2.9 KiB Raw Blame History

Dockerised end-to-end suite

Run

Coverage

Fixtures

2.9 KiB

Raw Blame History