slackhq/nebula
1
1
Fork 0
mirror of https://github.com/slackhq/nebula.git synced 2024-11-10 09:12:39 +08:00
Code Issues Projects Releases Packages Wiki Activity
nebula/Makefile

232 lines
6.5 KiB
Makefile
Raw Normal View History

make nebula a service that can install itself
2019-11-20 02:55:02 +08:00
NEBULA_CMD_PATH = "./cmd/nebula"
Use CGO_ENABLED=0 (#421) Set `CGO_ENABLED` to 0 when building
2021-11-05 02:20:44 +08:00
CGO_ENABLED = 0
export CGO_ENABLED
Public Release
2019-11-20 01:00:20 +08:00
Minor windows focused improvements (#443) Co-authored-by: Wade Simmons <wadey@slack-corp.com>
2021-05-01 04:04:47 +08:00
# Set up OS specific bits
ifeq ($(OS),Windows_NT)
NEBULA_CMD_SUFFIX = .exe
NULL_FILE = nul
Use registered io on Windows when possible (#905)
2023-07-11 01:43:48 +08:00
# RIO on windows does pointer stuff that makes go vet angry
VET_FLAGS = -unsafeptr=false
Minor windows focused improvements (#443) Co-authored-by: Wade Simmons <wadey@slack-corp.com>
2021-05-01 04:04:47 +08:00
else
NEBULA_CMD_SUFFIX =
NULL_FILE = /dev/null
endif
# Only defined the build number if we haven't already
ifndef BUILD_NUMBER
ifeq ($(shell git describe --exact-match 2>$(NULL_FILE)),)
BUILD_NUMBER = $(shell git describe --abbrev=0 --match "v*" | cut -dv -f2)-$(shell git branch --show-current)-$(shell git describe --long --dirty | cut -d- -f2-)
else
BUILD_NUMBER = $(shell git describe --exact-match --dirty | cut -dv -f2)
endif
Add a check in the makefile to ensure a minimum version of go is installed (#383)
2021-03-03 03:29:05 +08:00
endif
Push Docker images as part of the release workflow (#1037)
2024-05-02 21:37:11 +08:00
DOCKER_IMAGE_REPO ?= nebulaoss/nebula
DOCKER_IMAGE_TAG ?= latest
mips-softfloat (#231) This makes GOARM more generic and does GOMIPS in a similar way to support mips-softfloat. We also set `-ldflags "-s -w"` for mips-softfloat to give the best chance of the binary working on these small devices.
2020-06-27 01:46:23 +08:00
LDFLAGS = -X main.Build=$(BUILD_NUMBER)
GitHub Action: add release script (#124) This script will be triggered by any tag starting with `v[0-9]+.[0-9]+.[0-9]+` (i.e. v1.1.0). It will create all of the .tar.gz files (or .zip for windows). The amd64 binaries will be compiled on their target systems, the rest of the Linux architecures will be cross compiled from the Linux amd64 host. A SHASUM256.txt will also be generated and attached to the release.
2019-12-21 14:15:41 +08:00
ALL_LINUX = linux-amd64 \
fix whitespace
2019-12-21 02:55:15 +08:00
linux-386 \
linux-ppc64le \
make arm builds specific
2019-12-21 03:08:18 +08:00
linux-arm-5 \
fix whitespace
2019-12-21 02:55:15 +08:00
linux-arm-6 \
make arm builds specific
2019-12-21 03:08:18 +08:00
linux-arm-7 \
fix whitespace
2019-12-21 02:55:15 +08:00
linux-arm64 \
linux-mips \
linux-mipsle \
linux-mips64 \
mips-softfloat (#231) This makes GOARM more generic and does GOMIPS in a similar way to support mips-softfloat. We also set `-ldflags "-s -w"` for mips-softfloat to give the best chance of the binary working on these small devices.
2020-06-27 01:46:23 +08:00
linux-mips64le \
Fix build on riscv64 (#542) Add riscv64 build tag for udp_linux_64.go to fix build on riscv64 Co-authored-by: Wade Simmons <wade@wades.im>
2021-10-13 22:55:32 +08:00
linux-mips-softfloat \
Add support for LoongArch64 (#1003)
2024-04-30 22:55:44 +08:00
linux-riscv64 \
linux-loong64
GitHub Action: add release script (#124) This script will be triggered by any tag starting with `v[0-9]+.[0-9]+.[0-9]+` (i.e. v1.1.0). It will create all of the .tar.gz files (or .zip for windows). The amd64 binaries will be compiled on their target systems, the rest of the Linux architecures will be cross compiled from the Linux amd64 host. A SHASUM256.txt will also be generated and attached to the release.
2019-12-21 14:15:41 +08:00
Add support for naming FreeBSD tun devices (#903)
2023-06-23 00:13:31 +08:00
ALL_FREEBSD = freebsd-amd64 \
freebsd-arm64
Build for openbsd (#812)
2023-07-28 03:27:35 +08:00
ALL_OPENBSD = openbsd-amd64 \
openbsd-arm64
ALL_NETBSD = netbsd-amd64 \
netbsd-arm64
GitHub Action: add release script (#124) This script will be triggered by any tag starting with `v[0-9]+.[0-9]+.[0-9]+` (i.e. v1.1.0). It will create all of the .tar.gz files (or .zip for windows). The amd64 binaries will be compiled on their target systems, the rest of the Linux architecures will be cross compiled from the Linux amd64 host. A SHASUM256.txt will also be generated and attached to the release.
2019-12-21 14:15:41 +08:00
ALL = $(ALL_LINUX) \
Add support for naming FreeBSD tun devices (#903)
2023-06-23 00:13:31 +08:00
$(ALL_FREEBSD) \
Build for openbsd (#812)
2023-07-28 03:27:35 +08:00
$(ALL_OPENBSD) \
$(ALL_NETBSD) \
fix whitespace
2019-12-21 02:55:15 +08:00
darwin-amd64 \
Go 1.16 and darwin-arm64 (#381) This commit switches to Go 1.16 and adds a release binary for darwin-arm64. Fixes: #343
2021-02-18 02:11:57 +08:00
darwin-arm64 \
Add to build all windows-arm64 / bin-windows-arm64 build option (#638) * Add to build all windows-arm64 / bin-winarm64 builds * update release to build for windows-arm64 * cleanup Co-authored-by: Wade Simmons <wsimmons@slack-corp.com>
2022-03-19 01:23:10 +08:00
windows-amd64 \
Build for openbsd (#812)
2023-07-28 03:27:35 +08:00
windows-arm64
Makefile improvements Simplify the makefile by using implicit rules. The new structure for the build directory when using `make all` or `make release` is: build/$GOOS-$GOARCH-$GOARM/nebula (The GOARM part is optional, and only used for linux-arm-6) So, releases end up like `nebula-linux-amd64.tar.gz` or `nebula-linux-arm-6.tar.gz` This change also adds `-trimpath` to the build, to make the pathnames more generic in our releases.
2019-12-21 02:44:11 +08:00
Start of end to end testing with a good handshake between two nodes (#425)
2021-03-30 03:29:20 +08:00
e2e:
Simple lie test (#427)
2021-03-31 23:26:35 +08:00
$(TEST_ENV) go test -tags=e2e_testing -count=1 $(TEST_FLAGS) ./e2e
e2ev: TEST_FLAGS = -v
e2ev: e2e
e2evv: TEST_ENV += TEST_LOGS=1
e2evv: e2ev
e2evvv: TEST_ENV += TEST_LOGS=2
e2evvv: e2ev
e2evvvv: TEST_ENV += TEST_LOGS=3
e2evvvv: e2ev
Add a check in the makefile to ensure a minimum version of go is installed (#383)
2021-03-03 03:29:05 +08:00
Add a simple benchmark to e2e tests (#739)
2022-09-01 22:44:58 +08:00
e2e-bench: TEST_FLAGS = -bench=. -benchmem -run=^$
e2e-bench: e2e
Add Vagrant based smoke tests (#1067) * WIP smoke test freebsd * fix bitrot We now test that the firewall blocks inbound on host3 from host2 * WIP ipv6 test * cleanup * rename to make clear * fix filename * restore * no sudo docker * WIP * WIP * WIP * WIP * extra smoke tests * WIP * WIP * add over improvements made in smoke.sh * more tests * use generic/freebsd14 * cleanup from test * smoke test openbsd-amd64 * add netbsd-amd64 * try to fix vagrant
2024-04-30 23:02:16 +08:00
DOCKER_BIN = build/linux-amd64/nebula build/linux-amd64/nebula-cert
Makefile improvements Simplify the makefile by using implicit rules. The new structure for the build directory when using `make all` or `make release` is: build/$GOOS-$GOARCH-$GOARM/nebula (The GOARM part is optional, and only used for linux-arm-6) So, releases end up like `nebula-linux-amd64.tar.gz` or `nebula-linux-arm-6.tar.gz` This change also adds `-trimpath` to the build, to make the pathnames more generic in our releases.
2019-12-21 02:44:11 +08:00
all: $(ALL:%=build/%/nebula) $(ALL:%=build/%/nebula-cert)
Push Docker images as part of the release workflow (#1037)
2024-05-02 21:37:11 +08:00
docker: docker/linux-$(shell go env GOARCH)
Makefile improvements Simplify the makefile by using implicit rules. The new structure for the build directory when using `make all` or `make release` is: build/$GOOS-$GOARCH-$GOARM/nebula (The GOARM part is optional, and only used for linux-arm-6) So, releases end up like `nebula-linux-amd64.tar.gz` or `nebula-linux-arm-6.tar.gz` This change also adds `-trimpath` to the build, to make the pathnames more generic in our releases.
2019-12-21 02:44:11 +08:00
release: $(ALL:%=build/nebula-%.tar.gz)
Public Release
2019-11-20 01:00:20 +08:00
GitHub Action: add release script (#124) This script will be triggered by any tag starting with `v[0-9]+.[0-9]+.[0-9]+` (i.e. v1.1.0). It will create all of the .tar.gz files (or .zip for windows). The amd64 binaries will be compiled on their target systems, the rest of the Linux architecures will be cross compiled from the Linux amd64 host. A SHASUM256.txt will also be generated and attached to the release.
2019-12-21 14:15:41 +08:00
release-linux: $(ALL_LINUX:%=build/nebula-%.tar.gz)
Add support for naming FreeBSD tun devices (#903)
2023-06-23 00:13:31 +08:00
release-freebsd: $(ALL_FREEBSD:%=build/nebula-%.tar.gz)
Unbreak building for FreeBSD (#103) Add support for freebsd. You have to set `tun.dev` in your config. The second pass of this would be to remove the exec calls and use ioctl(2) and route(4) instead, but we can do that in a second PR. Co-authored-by: Wade Simmons <wade@wades.im>
2020-05-27 10:23:23 +08:00
Build for openbsd (#812)
2023-07-28 03:27:35 +08:00
release-openbsd: $(ALL_OPENBSD:%=build/nebula-%.tar.gz)
release-netbsd: $(ALL_NETBSD:%=build/nebula-%.tar.gz)
add boringcrypto Makefile targets (#856) This adds a few build targets to compile with `GOEXPERIMENT=boringcrypto`: - `bin-boringcrypto` - `release-boringcrypto` It also adds a field to the intial start up log indicating if boringcrypto is enabled in the binary.
2023-05-05 03:42:45 +08:00
release-boringcrypto: build/nebula-linux-$(shell go env GOARCH)-boringcrypto.tar.gz
add `make smoke-docker` (#287) This makes it easier to use the docker container smoke test that GitHub actions runs. There is also `make smoke-docker-race` that runs the smoke test with `-race` enabled.
2021-03-02 00:15:15 +08:00
BUILD_ARGS = -trimpath
better windows targets in Makefile (#125) This restores `make bin-windows` and also adds `make build/nebula-windows-amd64.zip` to build the zip file. Co-authored-by: Ryan Huber <rhuber@gmail.com>
2019-12-21 22:31:48 +08:00
bin-windows: build/windows-amd64/nebula.exe build/windows-amd64/nebula-cert.exe
mv $? .
Add to build all windows-arm64 / bin-windows-arm64 build option (#638) * Add to build all windows-arm64 / bin-winarm64 builds * update release to build for windows-arm64 * cleanup Co-authored-by: Wade Simmons <wsimmons@slack-corp.com>
2022-03-19 01:23:10 +08:00
bin-windows-arm64: build/windows-arm64/nebula.exe build/windows-arm64/nebula-cert.exe
mv $? .
better windows targets in Makefile (#125) This restores `make bin-windows` and also adds `make build/nebula-windows-amd64.zip` to build the zip file. Co-authored-by: Ryan Huber <rhuber@gmail.com>
2019-12-21 22:31:48 +08:00
bin-darwin: build/darwin-amd64/nebula build/darwin-amd64/nebula-cert
mv $? .
Unbreak building for FreeBSD (#103) Add support for freebsd. You have to set `tun.dev` in your config. The second pass of this would be to remove the exec calls and use ioctl(2) and route(4) instead, but we can do that in a second PR. Co-authored-by: Wade Simmons <wade@wades.im>
2020-05-27 10:23:23 +08:00
bin-freebsd: build/freebsd-amd64/nebula build/freebsd-amd64/nebula-cert
mv $? .
Add support for naming FreeBSD tun devices (#903)
2023-06-23 00:13:31 +08:00
bin-freebsd-arm64: build/freebsd-arm64/nebula build/freebsd-arm64/nebula-cert
mv $? .
add boringcrypto Makefile targets (#856) This adds a few build targets to compile with `GOEXPERIMENT=boringcrypto`: - `bin-boringcrypto` - `release-boringcrypto` It also adds a field to the intial start up log indicating if boringcrypto is enabled in the binary.
2023-05-05 03:42:45 +08:00
bin-boringcrypto: build/linux-$(shell go env GOARCH)-boringcrypto/nebula build/linux-$(shell go env GOARCH)-boringcrypto/nebula-cert
mv $? .
Public Release
2019-11-20 01:00:20 +08:00
bin:
Minor windows focused improvements (#443) Co-authored-by: Wade Simmons <wadey@slack-corp.com>
2021-05-01 04:04:47 +08:00
go build $(BUILD_ARGS) -ldflags "$(LDFLAGS)" -o ./nebula${NEBULA_CMD_SUFFIX} ${NEBULA_CMD_PATH}
go build $(BUILD_ARGS) -ldflags "$(LDFLAGS)" -o ./nebula-cert${NEBULA_CMD_SUFFIX} ./cmd/nebula-cert
Public Release
2019-11-20 01:00:20 +08:00
install:
add `make smoke-docker` (#287) This makes it easier to use the docker container smoke test that GitHub actions runs. There is also `make smoke-docker-race` that runs the smoke test with `-race` enabled.
2021-03-02 00:15:15 +08:00
go install $(BUILD_ARGS) -ldflags "$(LDFLAGS)" ${NEBULA_CMD_PATH}
go install $(BUILD_ARGS) -ldflags "$(LDFLAGS)" ./cmd/nebula-cert
mips-softfloat (#231) This makes GOARM more generic and does GOMIPS in a similar way to support mips-softfloat. We also set `-ldflags "-s -w"` for mips-softfloat to give the best chance of the binary working on these small devices.
2020-06-27 01:46:23 +08:00
build/linux-arm-%: GOENV += GOARM=$(word 3, $(subst -, ,$*))
build/linux-mips-%: GOENV += GOMIPS=$(word 3, $(subst -, ,$*))
# Build an extra small binary for mips-softfloat
build/linux-mips-softfloat/%: LDFLAGS += -s -w
Makefile improvements Simplify the makefile by using implicit rules. The new structure for the build directory when using `make all` or `make release` is: build/$GOOS-$GOARCH-$GOARM/nebula (The GOARM part is optional, and only used for linux-arm-6) So, releases end up like `nebula-linux-amd64.tar.gz` or `nebula-linux-arm-6.tar.gz` This change also adds `-trimpath` to the build, to make the pathnames more generic in our releases.
2019-12-21 02:44:11 +08:00
add boringcrypto Makefile targets (#856) This adds a few build targets to compile with `GOEXPERIMENT=boringcrypto`: - `bin-boringcrypto` - `release-boringcrypto` It also adds a field to the intial start up log indicating if boringcrypto is enabled in the binary.
2023-05-05 03:42:45 +08:00
# boringcrypto
build/linux-amd64-boringcrypto/%: GOENV += GOEXPERIMENT=boringcrypto CGO_ENABLED=1
build/linux-arm64-boringcrypto/%: GOENV += GOEXPERIMENT=boringcrypto CGO_ENABLED=1
Makefile improvements Simplify the makefile by using implicit rules. The new structure for the build directory when using `make all` or `make release` is: build/$GOOS-$GOARCH-$GOARM/nebula (The GOARM part is optional, and only used for linux-arm-6) So, releases end up like `nebula-linux-amd64.tar.gz` or `nebula-linux-arm-6.tar.gz` This change also adds `-trimpath` to the build, to make the pathnames more generic in our releases.
2019-12-21 02:44:11 +08:00
build/%/nebula: .FORCE
GOOS=$(firstword $(subst -, , $*)) \
mips-softfloat (#231) This makes GOARM more generic and does GOMIPS in a similar way to support mips-softfloat. We also set `-ldflags "-s -w"` for mips-softfloat to give the best chance of the binary working on these small devices.
2020-06-27 01:46:23 +08:00
GOARCH=$(word 2, $(subst -, ,$*)) $(GOENV) \
add `make smoke-docker` (#287) This makes it easier to use the docker container smoke test that GitHub actions runs. There is also `make smoke-docker-race` that runs the smoke test with `-race` enabled.
2021-03-02 00:15:15 +08:00
go build $(BUILD_ARGS) -o $@ -ldflags "$(LDFLAGS)" ${NEBULA_CMD_PATH}
Makefile improvements Simplify the makefile by using implicit rules. The new structure for the build directory when using `make all` or `make release` is: build/$GOOS-$GOARCH-$GOARM/nebula (The GOARM part is optional, and only used for linux-arm-6) So, releases end up like `nebula-linux-amd64.tar.gz` or `nebula-linux-arm-6.tar.gz` This change also adds `-trimpath` to the build, to make the pathnames more generic in our releases.
2019-12-21 02:44:11 +08:00
build/%/nebula-cert: .FORCE
GOOS=$(firstword $(subst -, , $*)) \
mips-softfloat (#231) This makes GOARM more generic and does GOMIPS in a similar way to support mips-softfloat. We also set `-ldflags "-s -w"` for mips-softfloat to give the best chance of the binary working on these small devices.
2020-06-27 01:46:23 +08:00
GOARCH=$(word 2, $(subst -, ,$*)) $(GOENV) \
add `make smoke-docker` (#287) This makes it easier to use the docker container smoke test that GitHub actions runs. There is also `make smoke-docker-race` that runs the smoke test with `-race` enabled.
2021-03-02 00:15:15 +08:00
go build $(BUILD_ARGS) -o $@ -ldflags "$(LDFLAGS)" ./cmd/nebula-cert
Makefile improvements Simplify the makefile by using implicit rules. The new structure for the build directory when using `make all` or `make release` is: build/$GOOS-$GOARCH-$GOARM/nebula (The GOARM part is optional, and only used for linux-arm-6) So, releases end up like `nebula-linux-amd64.tar.gz` or `nebula-linux-arm-6.tar.gz` This change also adds `-trimpath` to the build, to make the pathnames more generic in our releases.
2019-12-21 02:44:11 +08:00
better windows targets in Makefile (#125) This restores `make bin-windows` and also adds `make build/nebula-windows-amd64.zip` to build the zip file. Co-authored-by: Ryan Huber <rhuber@gmail.com>
2019-12-21 22:31:48 +08:00
build/%/nebula.exe: build/%/nebula
mv $< $@
build/%/nebula-cert.exe: build/%/nebula-cert
mv $< $@
Makefile improvements Simplify the makefile by using implicit rules. The new structure for the build directory when using `make all` or `make release` is: build/$GOOS-$GOARCH-$GOARM/nebula (The GOARM part is optional, and only used for linux-arm-6) So, releases end up like `nebula-linux-amd64.tar.gz` or `nebula-linux-arm-6.tar.gz` This change also adds `-trimpath` to the build, to make the pathnames more generic in our releases.
2019-12-21 02:44:11 +08:00
build/nebula-%.tar.gz: build/%/nebula build/%/nebula-cert
tar -zcv -C build/$* -f $@ nebula nebula-cert
Public Release
2019-11-20 01:00:20 +08:00
better windows targets in Makefile (#125) This restores `make bin-windows` and also adds `make build/nebula-windows-amd64.zip` to build the zip file. Co-authored-by: Ryan Huber <rhuber@gmail.com>
2019-12-21 22:31:48 +08:00
build/nebula-%.zip: build/%/nebula.exe build/%/nebula-cert.exe
cd build/$* && zip ../nebula-$*.zip nebula.exe nebula-cert.exe
Push Docker images as part of the release workflow (#1037)
2024-05-02 21:37:11 +08:00
docker/%: build/%/nebula build/%/nebula-cert
docker build . $(DOCKER_BUILD_ARGS) -f docker/Dockerfile --platform "$(subst -,/,$*)" --tag "${DOCKER_IMAGE_REPO}:${DOCKER_IMAGE_TAG}" --tag "${DOCKER_IMAGE_REPO}:$(BUILD_NUMBER)"
Public Release
2019-11-20 01:00:20 +08:00
vet:
Use registered io on Windows when possible (#905)
2023-07-11 01:43:48 +08:00
go vet $(VET_FLAGS) -v ./...
Public Release
2019-11-20 01:00:20 +08:00
test:
go test -v ./...
add test for GOEXPERIMENT=boringcrypto (#861) * add test for GOEXPERIMENT=boringcrypto * fix NebulaCertificate.Sign Set the PublicKey field in a more compatible way for the tests. The current method grabs the public key from the certificate, but the correct thing to do is to derive it from the private key. Either way doesn't really matter as I don't think the Sign method actually even uses the PublicKey field. * assert boring * cleanup tests
2023-05-09 01:27:01 +08:00
test-boringcrypto:
GOEXPERIMENT=boringcrypto CGO_ENABLED=1 go test -v ./...
Public Release
2019-11-20 01:00:20 +08:00
test-cov-html:
go test -coverprofile=coverage.out
go tool cover -html=coverage.out
test: build all non-main modules for mobile (#1036) Ensure that we don't break the build for mobile by doing a `go build` for all of the non-main modules in the repo. Should hopefully catch issues like #1035 sooner.
2023-12-22 00:59:21 +08:00
build-test-mobile:
GOARCH=amd64 GOOS=ios go build $(shell go list ./... | grep -v '/cmd/\|/examples/')
GOARCH=arm64 GOOS=ios go build $(shell go list ./... | grep -v '/cmd/\|/examples/')
GOARCH=amd64 GOOS=android go build $(shell go list ./... | grep -v '/cmd/\|/examples/')
GOARCH=arm64 GOOS=android go build $(shell go list ./... | grep -v '/cmd/\|/examples/')
Public Release
2019-11-20 01:00:20 +08:00
bench:
go test -bench=.
bench-cpu:
go test -bench=. -benchtime=5s -cpuprofile=cpu.pprof
go tool pprof go-audit.test cpu.pprof
bench-cpu-long:
go test -bench=. -benchtime=60s -cpuprofile=cpu.pprof
go tool pprof go-audit.test cpu.pprof
proto: nebula.pb.go cert/cert.pb.go
nebula.pb.go: nebula.proto .FORCE
Lighthouse performance pass (#418)
2021-04-01 06:32:02 +08:00
go build github.com/gogo/protobuf/protoc-gen-gogofaster
More LH cleanup (#429)
2021-04-01 23:23:31 +08:00
PATH="$(CURDIR):$(PATH)" protoc --gogofaster_out=paths=source_relative:. $<
Lighthouse performance pass (#418)
2021-04-01 06:32:02 +08:00
rm protoc-gen-gogofaster
Public Release
2019-11-20 01:00:20 +08:00
cert/cert.pb.go: cert/cert.proto .FORCE
$(MAKE) -C cert cert.pb.go
make nebula a service that can install itself
2019-11-20 02:55:02 +08:00
service:
Minor windows focused improvements (#443) Co-authored-by: Wade Simmons <wadey@slack-corp.com>
2021-05-01 04:04:47 +08:00
@echo > $(NULL_FILE)
make nebula a service that can install itself
2019-11-20 02:55:02 +08:00
$(eval NEBULA_CMD_PATH := "./cmd/nebula-service")
ifeq ($(words $(MAKECMDGOALS)),1)
Minor windows focused improvements (#443) Co-authored-by: Wade Simmons <wadey@slack-corp.com>
2021-05-01 04:04:47 +08:00
@$(MAKE) service ${.DEFAULT_GOAL} --no-print-directory
make nebula a service that can install itself
2019-11-20 02:55:02 +08:00
endif
add `make smoke-docker` (#287) This makes it easier to use the docker container smoke test that GitHub actions runs. There is also `make smoke-docker-race` that runs the smoke test with `-race` enabled.
2021-03-02 00:15:15 +08:00
bin-docker: bin build/linux-amd64/nebula build/linux-amd64/nebula-cert
smoke-docker: bin-docker
cd .github/workflows/smoke/ && ./build.sh
cd .github/workflows/smoke/ && ./smoke.sh
Support NIST curve P256 (#769) * Support NIST curve P256 This change adds support for NIST curve P256. When you use `nebula-cert ca` or `nebula-cert keygen`, you can specify `-curve P256` to enable it. The curve to use is based on the curve defined in your CA certificate. Internally, we use ECDSA P256 to sign certificates, and ECDH P256 to do Noise handshakes. P256 is not supported natively in Noise Protocol, so we define `DHP256` in the `noiseutil` package to implement support for it. You cannot have a mixed network of Curve25519 and P256 certificates, since the Noise protocol will only attempt to parse using the Curve defined in the host's certificate. * verify the curves match in VerifyPrivateKey This would have failed anyways once we tried to actually use the bytes in the private key, but its better to detect the issue up front with a better error message. * add cert.Curve argument to Sign method * fix mismerge * use crypto/ecdh This is the preferred method for doing ECDH functions now, and also has a boringcrypto specific codepath. * remove other ecdh uses of crypto/elliptic use crypto/ecdh instead
2023-05-05 05:50:23 +08:00
cd .github/workflows/smoke/ && NAME="smoke-p256" CURVE="P256" ./build.sh
cd .github/workflows/smoke/ && NAME="smoke-p256" ./smoke.sh
add `make smoke-docker` (#287) This makes it easier to use the docker container smoke test that GitHub actions runs. There is also `make smoke-docker-race` that runs the smoke test with `-race` enabled.
2021-03-02 00:15:15 +08:00
Relay (#678) Co-authored-by: Wade Simmons <wsimmons@slack-corp.com>
2022-06-22 02:35:23 +08:00
smoke-relay-docker: bin-docker
cd .github/workflows/smoke/ && ./build-relay.sh
cd .github/workflows/smoke/ && ./smoke-relay.sh
add `make smoke-docker` (#287) This makes it easier to use the docker container smoke test that GitHub actions runs. There is also `make smoke-docker-race` that runs the smoke test with `-race` enabled.
2021-03-02 00:15:15 +08:00
smoke-docker-race: BUILD_ARGS = -race
github actions smoke-test: run with data race detector (#988) Run the github actions smoke tests with data race detector enabled, so we can detect if a PR introduces a simple data race.
2023-10-31 22:32:39 +08:00
smoke-docker-race: CGO_ENABLED = 1
add `make smoke-docker` (#287) This makes it easier to use the docker container smoke test that GitHub actions runs. There is also `make smoke-docker-race` that runs the smoke test with `-race` enabled.
2021-03-02 00:15:15 +08:00
smoke-docker-race: smoke-docker
Add Vagrant based smoke tests (#1067) * WIP smoke test freebsd * fix bitrot We now test that the firewall blocks inbound on host3 from host2 * WIP ipv6 test * cleanup * rename to make clear * fix filename * restore * no sudo docker * WIP * WIP * WIP * WIP * extra smoke tests * WIP * WIP * add over improvements made in smoke.sh * more tests * use generic/freebsd14 * cleanup from test * smoke test openbsd-amd64 * add netbsd-amd64 * try to fix vagrant
2024-04-30 23:02:16 +08:00
smoke-vagrant/%: bin-docker build/%/nebula
cd .github/workflows/smoke/ && ./build.sh $*
cd .github/workflows/smoke/ && ./smoke-vagrant.sh $*
Public Release
2019-11-20 01:00:20 +08:00
.FORCE:
Add Vagrant based smoke tests (#1067) * WIP smoke test freebsd * fix bitrot We now test that the firewall blocks inbound on host3 from host2 * WIP ipv6 test * cleanup * rename to make clear * fix filename * restore * no sudo docker * WIP * WIP * WIP * WIP * extra smoke tests * WIP * WIP * add over improvements made in smoke.sh * more tests * use generic/freebsd14 * cleanup from test * smoke test openbsd-amd64 * add netbsd-amd64 * try to fix vagrant
2024-04-30 23:02:16 +08:00
.PHONY: bench bench-cpu bench-cpu-long bin build-test-mobile e2e e2ev e2evv e2evvv e2evvvv proto release service smoke-docker smoke-docker-race test test-cov-html smoke-vagrant/%
Public Release
2019-11-20 01:00:20 +08:00
.DEFAULT_GOAL := bin
Reference in a new issue Copy permalink