<build artifact type>:<language>
singlecommands, and in the composition file for
exec:gobuilder uses the machine's own Go installation to compile and build a binary. Below are the options this builder supports. None of these are required and need only be edited if the defaults do not work well in your environment.
docker:gobuilder uses the user's local Docker daemon to construct a Docker image. By default, the
docker:gobuilder will leverage a
goproxycontainer to speed up fetching of Go modules. Additionally, all builds are performed on an isolated Docker network.
go_proxy_modeis custom. Use a custom go_proxy instance.
manifest.tomlfile, consisting of a
builder => paths, which specify which paths to include as extras for each builders.
docker:gobuild, you could add this snippet to the plan's manifest:
exec:gobuilder. This command will produce a binary which you can find in
~/testground/on Linux and macOS systems.
docker:gobuilder. This command will produce a Docker image.
barrier-local.toml. Note that the composition file will contain the builder and runner so specifying the builder on the command-line is not used in this example.