mirror of
https://github.com/docker/compose.git
synced 2025-07-25 06:34:35 +02:00
3c5d37326d
This approach allows better caching of results (so faster subsequent lints). It also avoids bind mounts which are slow. Benchmarks on my machine (2017 MacBook Pro 13"): * bind mount lint: 2m 38s * new lint (after docker builder prune): 1m 35s * old lint (rerun no changes): 2m 38s * new lint (rerun added println in random Go file): 9s Signed-off-by: Christopher Crone <christopher.crone@docker.com>
Docker API
Dev Setup
The recommended way is to use the main Makefile that runs everything inside a container.
If you don't have or want to use Docker for building you need to make sure you have all the needed tools installed locally:
- go 1.14
- protoc
go get github.com/golang/protobuf/protoc-gen-go@v1.4.1go get golang.org/x/tools/cmd/goimportsgo get github.com/golangci/golangci-lint/cmd/golangci-lint@v1.26.0
And then you can call the same make targets but you need to pass it the builder.Makefile (make -f builder.Makefile).
The new CLI delegates to the classic docker for default contexts ; delegation is done to docker-classic.
make classic-linkwill create adocker-classiclink in/usr/local/binif you don't already have it from Docker Desktop
Building the project
$ make
If you make changes to the .proto files, make sure to make protos to generate go code.
Tests
To run unit tests:
make test
If you need to update a golden file simply do go test ./... -test.update-golden.