Stitch any CI into Tangled
151
fork

Configure Feed

Select the types of activity you want to include in your feed.

build: add Docker image CI smoke test #16

open opened by mitchellh.com targeting main from push-unqpnvkxlrnp

Fixes #3

Add a community Dockerfile for tack and cover it in Buildkite so it does not drift unnoticed. The Docker build uses the Go version pinned by go.mod, installs CA certificates in a slim Debian runtime image, and keeps common local artifacts out of the Docker build context.

The new Buildkite step builds the image and runs tack -h, matching the existing Nix package smoke test without requiring runtime configuration, credentials, or external services.

Labels

None yet.

assignee

None yet.

Participants 1
AT URI
at://did:plc:onu3oqfahfubgbetlr4giknc/sh.tangled.repo.pull/3ml7ixg5shq22
+6 -1
Interdiff #0 #1
+6 -1
.buildkite/pipeline.yml
··· 37 37 # The image smoke test mirrors the Nix package smoke test: `tack -h` exits 38 38 # before env-var validation, so it proves the container starts without 39 39 # needing a database, Tangled credentials, or a live HTTP listener. 40 + # 41 + # Buildkite's Docker builder may be a remote BuildKit driver, so `--load` 42 + # makes the tagged image available to the local daemon for `docker run`. 43 + # `--quiet` also keeps the layer transfer logs below Buildkite's display 44 + # limit while still surfacing a failing Dockerfile command. 40 45 command: | 41 - docker build --pull --file docker/tack.Dockerfile --tag tack:ci . 46 + docker build --pull --load --quiet --file docker/tack.Dockerfile --tag tack:ci . 42 47 docker run --rm tack:ci /app/bin/tack -h
.dockerignore

This file has not been changed.

docker/tack.Dockerfile

This file has not been changed.

History

2 rounds 0 comments
sign up or login to add to the discussion
1 commit
expand
build: add Docker image CI smoke test
merge conflicts detected
expand
  • .buildkite/pipeline.yml:31
expand 0 comments
1 commit
expand
build: add Docker image CI smoke test
expand 0 comments