bb5542e26e
- Both FetchContainer and DockerBuild read the image metadata and convert to LLB (e.g. `ENV foo bar` in Dockerfile shows up in `op.#Exec`) - Image metadata is "sticky" between Pipelines (e.g. `op.#Load` will re-use the same metadata) - Image metadata is injected back to #PushContainer, so that DockerBuild+PushContainer and FetchContainer+PushContainer do not lose any metadata. - Tests for all the above Fixes #142 Signed-off-by: Andrea Luzzardi <aluzzardi@gmail.com> |
||
|---|---|---|
| .. | ||
| cli | ||
| compute | ||
| examples/react | ||
| llb | ||
| stdlib | ||
| README.md | ||
| test-cli.sh | ||
| test-compute.sh | ||
| test-examples.sh | ||
| test-lib.sh | ||
| test-llb.sh | ||
| test-stdlib.sh | ||
| test-test.sh | ||
| test.sh | ||
Testing
TL;DR
# Get help
./test.sh --help
# Run all tests
# You can also just call ./test.sh with no argument
# Also, `make integration` does exactly that
./test.sh all
# Run one random dagger cue directory, with expectations on exit code, stdout, stderr
./test.sh fetch-git/nonexistent/ref --exit=1 --stdout=
By default, the dagger binary is expected to be found in ../../cmd/dagger/dagger relative to the test.sh script.
If you need to change this, pass along DAGGER_BINARY=somewhere/dagger