Closed gebn closed 4 years ago
go_binary
's out
attribute may come in handy. Can have multiple go_binary
rules and trigger them as needed. //:plexbackup
can remain Linux/amd64.
No, the correct way to do this is documented here, so you'll need to run bazel build --platforms=@io_bazel_rules_go//go/toolchain:<arch> --incompatible_no_support_tools_in_action_inputs=false plexbackup
with:
windows_amd64
linux_arm64
darwin_amd64
The --platforms
flag forces pure mode, so #20 is now somewhat moot.
N.B. given you're using --all_incompatible_changes
, you'll need to pass --incompatible_no_support_tools_in_action_inputs=false
until rules_go
is updated.
Bazel's job is to produce a single directory containing all release assets so a simple glob can be given to the GitHub releases provided in Travis.
E.g.
plexbackup-1.0.0-darwin-x86_64
plexbackup-1.0.0-darwin-x86_64.sha256
plexbackup-1.0.0-linux-x86_64
plexbackup-1.0.0-linux-x86_64.sha256
plexbackup-1.0.0-windows-x86_64.exe
plexbackup-1.0.0-windows-x86_64.exe.sha256
Considered compression, however other projects like Bazel do not do this.