go/goreleaser
go/goreleaser
1
0
Fork 0
mirror of https://github.com/goreleaser/goreleaser.git synced 2025-03-17 20:47:50 +02:00
Code Issues Releases Activity

docs: goreleaser build

Browse Source 
Signed-off-by: Carlos A Becker <caarlos0@gmail.com>
This commit is contained in:
Carlos A Becker 2021-11-30 10:41:50 -03:00
parent eb4bee7f13
commit 6a30b0e55d
No known key found for this signature in database
GPG Key ID: E61E2F7DC14AB940
1 changed files with 12 additions and 3 deletions

15
www/docs/cmd/goreleaser_build.md

@ -4,11 +4,20 @@ Builds the current project
## Synopsis
The build command allows you to execute only a subset of the pipeline, i.e. only the build step with its dependencies.
The `goreleaser build` command is analogous to the
`go build` command, in the sense it only builds binaries.
It allows you to quickly check if your GoReleaser build configurations are doing what you expect.
Its itented usage is, for example, within Makefiles to avoid setting up
ldflags and etc in several places. That way, the GoReleaser config becomes the
source of truth for how the binaries should be built.
Finally, it allows you to generate a local build for your current machine only using the `--single-target` option, and specific build IDs using the `--id` option.
It also allows you to generate a local build for your current machine only using
the `--single-target` option, and specific build IDs using the
`--id` option in case you have more than one.
When using `--single-target`, the `GOOS` and
`GOARCH` environment variables are used to determine the target,
defaulting to the current's machine target if not set.
```