Kiu/VictoriaMetrics
Kiu/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2024-11-23 12:31:07 +01:00
Code Issues Actions 8 Packages Projects Releases Wiki Activity
7454d938cc
VictoriaMetrics/Makefile

589 lines
18 KiB
Makefile
Raw Normal View History

all: open-sourcing single-node version
2019-05-22 23:16:55 +02:00
PKG_PREFIX := github.com/VictoriaMetrics/VictoriaMetrics
Follow up after https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5685 (#5686)
2024-01-25 10:03:46 +01:00
MAKE_CONCURRENCY ?= $(shell getconf _NPROCESSORS_ONLN)
Makefile: allow specifying the needed concurrency for make via MAKE_CONCURRENCY env var
2023-11-20 23:55:19 +01:00
MAKE_PARALLEL := $(MAKE) -j $(MAKE_CONCURRENCY)
Allow specifying build date from a variable (#1200) Just like the existing infrastructure for `BUILDINFO_TAG`, this can ease the production of [reproducible builds](https://wiki.freebsd.org/ReproducibleBuilds). (e.g. in FreeBSD the date the port was committed is used at build time, not the actual build time, so that an identical port produced at different times produces an identical executable)
2021-04-10 14:46:53 +02:00
DATEINFO_TAG ?= $(shell date -u +'%Y%m%d-%H%M%S')
all: open-sourcing single-node version
2019-05-22 23:16:55 +02:00
BUILDINFO_TAG ?= $(shell echo $$(git describe --long --all | tr '/' '-')$$( \
make: make openssl output parsing symbol number agnostic (#3429)
2022-12-01 16:09:36 +01:00
git diff-index --quiet HEAD -- || echo '-dirty-'$$(git diff-index -u HEAD | openssl sha1 | cut -d' ' -f2 | cut -c 1-8)))
build: nightly builds at 2:48am (#3490)
2022-12-17 01:46:24 +01:00
LATEST_TAG ?= latest
all: open-sourcing single-node version
2019-05-22 23:16:55 +02:00
PKG_TAG ?= $(shell git tag -l --points-at HEAD)
ifeq ($(PKG_TAG),)
PKG_TAG := $(BUILDINFO_TAG)
endif
Allow specifying build date from a variable (#1200) Just like the existing infrastructure for `BUILDINFO_TAG`, this can ease the production of [reproducible builds](https://wiki.freebsd.org/ReproducibleBuilds). (e.g. in FreeBSD the date the port was committed is used at build time, not the actual build time, so that an identical port produced at different times produces an identical executable)
2021-04-10 14:46:53 +02:00
GO_BUILDINFO = -X '$(PKG_PREFIX)/lib/buildinfo.Version=$(APP_NAME)-$(DATEINFO_TAG)-$(BUILDINFO_TAG)'
make: reset permissions when creating release archive (#6846) ### Describe Your Changes Forcefully set permissions for release binaries to 1000:1000. This helps to avoid issues such as https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6788 on systems with limitations around UID:GID configuration. "1000" UID and GID is widely used by linux distributions for the first user in the system. ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com>
2024-08-21 11:25:13 +02:00
TAR_OWNERSHIP ?= --owner=1000 --group=1000
all: open-sourcing single-node version
2019-05-22 23:16:55 +02:00
Makefile: force running Makefile rules if there is a file matching their names
2020-12-18 11:20:01 +01:00
.PHONY: $(MAKECMDGOALS)
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
include app/*/Makefile
docs: add spellcheck command (#6562) ### Describe Your Changes Implement spellcheck command: - add cspell configuration files - dockerize spellchecking process - add Makefile targets This PR adds a standalone `make spellcheck` target to check `docs/*.md` files for spelling errors. The target process is dockerized to be run in a separate npm environment. Some `docs/` typo fixes also included. ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Arkadii Yakovets <ark@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com>
2024-07-11 12:39:42 +02:00
include cspell/Makefile
docs: convert png images to webp in all the docs except of docs/operator/* This reduces the size of docs/* folder from 33MB to 18MB Images inside docs/operator/* must be converted at the https://github.com/VictoriaMetrics/operator/tree/master/docs and then the updated images must be automatically propagated to the docs/operator/* This is a follow-up for d3f919df3eb172a7779b94efb442402215fd0581 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5206
2023-11-22 17:22:41 +01:00
include docs/Makefile
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
include deployment/*/Makefile
dashboards: provide copies of Grafana dashboards alternated with Vict… (#4905) dashboards: provide copies of Grafana dashboards alternated with VictoriaMetrics datasource Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-08-29 11:06:55 +02:00
include dashboards/Makefile
simplify release process (#3012) * simplify release process * address comments * address comments * wip * wip * wip Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2022-08-31 01:27:24 +02:00
include package/release/Makefile
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
all: open-sourcing single-node version
2019-05-22 23:16:55 +02:00
all: \
app/vmagent: initial implementation for vmagent
2020-02-23 12:35:47 +01:00
victoria-metrics-prod \
app/victoria-logs: initial code release
2023-06-20 07:55:12 +02:00
victoria-logs-prod \
app/vlogscli: add interactive command-line tool for querying VictoriaLogs
2024-10-01 12:08:17 +02:00
vlogscli-prod \
app/vmagent: initial implementation for vmagent
2020-02-23 12:35:47 +01:00
vmagent-prod \
app/vmauth: add initial version of vmauth. See https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/app/vmauth/README.md for details
2020-05-05 09:53:42 +02:00
vmalert-prod \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
vmalert-tool-prod \
app/vmauth: add initial version of vmauth. See https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/app/vmauth/README.md for details
2020-05-05 09:53:42 +02:00
vmauth-prod \
app/vmagent: initial implementation for vmagent
2020-02-23 12:35:47 +01:00
vmbackup-prod \
app/vmctl: move vmctl code from github.com/VictoriaMetrics/vmctl It is better developing vmctl tool in VictoriaMetrics repository, so it could be released together with the rest of vmutils tools such as vmalert, vmagent, vmbackup, vmrestore and vmauth.
2021-02-01 00:10:16 +01:00
vmrestore-prod \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
vmctl-prod
all: open-sourcing single-node version
2019-05-22 23:16:55 +02:00
clean:
rm -rf bin/*
Makefile: remove package-base dependency from `publish` rule, since this dep is set inside all the `publish-*` dependencies This is a follow-up for d4099a75be7ad7ae906b4c8a6820ffb204f0de77
2023-11-15 12:22:37 +01:00
publish: \
app/{vmbackup,vmrestore}: add `vmbackup` and `vmrestore` tools for creating backups on s3 or gcs from instant snapshots Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/203 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/38
2019-11-07 20:05:39 +01:00
publish-victoria-metrics \
app/vmagent: initial implementation for vmagent
2020-02-23 12:35:47 +01:00
publish-vmagent \
app/vmalert: include it into the next release
2020-04-27 23:09:35 +02:00
publish-vmalert \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
publish-vmalert-tool \
app/vmauth: add initial version of vmauth. See https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/app/vmauth/README.md for details
2020-05-05 09:53:42 +02:00
publish-vmauth \
app/{vmbackup,vmrestore}: add `vmbackup` and `vmrestore` tools for creating backups on s3 or gcs from instant snapshots Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/203 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/38
2019-11-07 20:05:39 +01:00
publish-vmbackup \
app/vmctl: move vmctl code from github.com/VictoriaMetrics/vmctl It is better developing vmctl tool in VictoriaMetrics repository, so it could be released together with the rest of vmutils tools such as vmalert, vmagent, vmbackup, vmrestore and vmauth.
2021-02-01 00:10:16 +01:00
publish-vmrestore \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
publish-vmctl
Makefile: add `make publish` and `make package` shortcuts for building and publishing docker images
2019-05-24 12:19:24 +02:00
app/{vmbackup,vmrestore}: add `vmbackup` and `vmrestore` tools for creating backups on s3 or gcs from instant snapshots Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/203 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/38
2019-11-07 20:05:39 +01:00
package: \
package-victoria-metrics \
app/victoria-logs: initial code release
2023-06-20 07:55:12 +02:00
package-victoria-logs \
app/vlogscli: add interactive command-line tool for querying VictoriaLogs
2024-10-01 12:08:17 +02:00
package-vlogscli \
app/vmagent: initial implementation for vmagent
2020-02-23 12:35:47 +01:00
package-vmagent \
app/vmalert: include it into the next release
2020-04-27 23:09:35 +02:00
package-vmalert \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
package-vmalert-tool \
app/vmauth: add initial version of vmauth. See https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/app/vmauth/README.md for details
2020-05-05 09:53:42 +02:00
package-vmauth \
app/{vmbackup,vmrestore}: add `vmbackup` and `vmrestore` tools for creating backups on s3 or gcs from instant snapshots Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/203 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/38
2019-11-07 20:05:39 +01:00
package-vmbackup \
app/vmctl: move vmctl code from github.com/VictoriaMetrics/vmctl It is better developing vmctl tool in VictoriaMetrics repository, so it could be released together with the rest of vmutils tools such as vmalert, vmagent, vmbackup, vmrestore and vmauth.
2021-02-01 00:10:16 +01:00
package-vmrestore \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
package-vmctl
Makefile: add `make publish` and `make package` shortcuts for building and publishing docker images
2019-05-24 12:19:24 +02:00
Makefile: localize parallel make to `release`, `release-victoria-logs` and `crossbuild` commands This is a follow-up for 81ddee4f3ac85b6d97c3d9a57a4f3c3c343c76ca
2023-11-20 22:15:07 +01:00
vmutils: \
vmagent \
vmalert \
vmalert-tool \
vmauth \
vmbackup \
vmrestore \
vmctl
vmutils-pure: \
vmagent-pure \
vmalert-pure \
vmalert-tool-pure \
vmauth-pure \
vmbackup-pure \
vmrestore-pure \
vmctl-pure
vmutils-linux-amd64: \
vmagent-linux-amd64 \
vmalert-linux-amd64 \
vmalert-tool-linux-amd64 \
vmauth-linux-amd64 \
vmbackup-linux-amd64 \
vmrestore-linux-amd64 \
vmctl-linux-amd64
vmutils-linux-arm64: \
vmagent-linux-arm64 \
vmalert-linux-arm64 \
vmalert-tool-linux-arm64 \
vmauth-linux-arm64 \
vmbackup-linux-arm64 \
vmrestore-linux-arm64 \
vmctl-linux-arm64
vmutils-linux-arm: \
vmagent-linux-arm \
vmalert-linux-arm \
vmalert-tool-linux-arm \
vmauth-linux-arm \
vmbackup-linux-arm \
vmrestore-linux-arm \
vmctl-linux-arm
vmutils-linux-386: \
vmagent-linux-386 \
vmalert-linux-386 \
vmalert-tool-linux-386 \
vmauth-linux-386 \
vmbackup-linux-386 \
vmrestore-linux-386 \
vmctl-linux-386
vmutils-linux-ppc64le: \
vmagent-linux-ppc64le \
vmalert-linux-ppc64le \
vmalert-tool-linux-ppc64le \
vmauth-linux-ppc64le \
vmbackup-linux-ppc64le \
vmrestore-linux-ppc64le \
vmctl-linux-ppc64le
vmutils-darwin-amd64: \
vmagent-darwin-amd64 \
vmalert-darwin-amd64 \
vmalert-tool-darwin-amd64 \
vmauth-darwin-amd64 \
vmbackup-darwin-amd64 \
vmrestore-darwin-amd64 \
vmctl-darwin-amd64
vmutils-darwin-arm64: \
vmagent-darwin-arm64 \
vmalert-darwin-arm64 \
vmalert-tool-darwin-arm64 \
vmauth-darwin-arm64 \
vmbackup-darwin-arm64 \
vmrestore-darwin-arm64 \
vmctl-darwin-arm64
vmutils-freebsd-amd64: \
vmagent-freebsd-amd64 \
vmalert-freebsd-amd64 \
vmalert-tool-freebsd-amd64 \
vmauth-freebsd-amd64 \
vmbackup-freebsd-amd64 \
vmrestore-freebsd-amd64 \
vmctl-freebsd-amd64
vmutils-openbsd-amd64: \
vmagent-openbsd-amd64 \
vmalert-openbsd-amd64 \
vmalert-tool-openbsd-amd64 \
vmauth-openbsd-amd64 \
vmbackup-openbsd-amd64 \
vmrestore-openbsd-amd64 \
vmctl-openbsd-amd64
vmutils-windows-amd64: \
vmagent-windows-amd64 \
vmalert-windows-amd64 \
vmalert-tool-windows-amd64 \
vmauth-windows-amd64 \
vmbackup-windows-amd64 \
vmrestore-windows-amd64 \
vmctl-windows-amd64
crossbuild:
$(MAKE_PARALLEL) victoria-metrics-crossbuild vmutils-crossbuild
victoria-metrics-crossbuild: \
victoria-metrics-linux-386 \
victoria-metrics-linux-amd64 \
victoria-metrics-linux-arm64 \
victoria-metrics-linux-arm \
victoria-metrics-linux-ppc64le \
victoria-metrics-darwin-amd64 \
victoria-metrics-darwin-arm64 \
victoria-metrics-freebsd-amd64 \
Makefile: add VictoriaMetrics Windows build into crossbuild
2024-02-07 21:27:05 +01:00
victoria-metrics-openbsd-amd64 \
victoria-metrics-windows-amd64
Makefile: localize parallel make to `release`, `release-victoria-logs` and `crossbuild` commands This is a follow-up for 81ddee4f3ac85b6d97c3d9a57a4f3c3c343c76ca
2023-11-20 22:15:07 +01:00
vmutils-crossbuild: \
vmutils-linux-386 \
vmutils-linux-amd64 \
vmutils-linux-arm64 \
vmutils-linux-arm \
vmutils-linux-ppc64le \
vmutils-darwin-amd64 \
vmutils-darwin-arm64 \
vmutils-freebsd-amd64 \
vmutils-openbsd-amd64 \
vmutils-windows-amd64
Snap docs change (#986) * adds snap docs, adds release information for snap package, adds docs notes about configuration management with snap package. * adds release page mention * version fix for snap, its awful * revert version * Apply suggestions from code review Co-authored-by: Aliaksandr Valialkin <valyala@gmail.com>
2020-12-29 10:43:09 +01:00
Makefile: add `TAG=v... make publish-release` rule for building and publishing a release for the given TAG
2021-11-08 11:29:10 +01:00
publish-release:
Makefile: cleanup bin/ directory at the beginning of `make publish-release` command This is needed in order to prevent from non-build artifacts to be uploaded to Github release page
2023-08-29 13:10:27 +02:00
rm -rf bin/*
Makefile: speedup `release`, `publish` and `crossbuild` rules by using parallel make
2023-11-20 21:51:33 +01:00
git checkout $(TAG) && $(MAKE) release && LATEST_TAG=stable $(MAKE) publish && \
git checkout $(TAG)-cluster && $(MAKE) release && LATEST_TAG=cluster-stable $(MAKE) publish && \
git checkout $(TAG)-enterprise && $(MAKE) release && LATEST_TAG=enterprise-stable $(MAKE) publish && \
git checkout $(TAG)-enterprise-cluster && $(MAKE) release && LATEST_TAG=enterprise-cluster-stable $(MAKE) publish
Makefile: add `TAG=v... make publish-release` rule for building and publishing a release for the given TAG
2021-11-08 11:29:10 +01:00
Makefile: localize parallel make to `release`, `release-victoria-logs` and `crossbuild` commands This is a follow-up for 81ddee4f3ac85b6d97c3d9a57a4f3c3c343c76ca
2023-11-20 22:15:07 +01:00
release:
$(MAKE_PARALLEL) \
release-victoria-metrics \
release-vmutils
release-victoria-metrics: \
release-victoria-metrics-linux-386 \
release-victoria-metrics-linux-amd64 \
release-victoria-metrics-linux-arm \
release-victoria-metrics-linux-arm64 \
release-victoria-metrics-darwin-amd64 \
release-victoria-metrics-darwin-arm64 \
release-victoria-metrics-freebsd-amd64 \
release-victoria-metrics-openbsd-amd64 \
release-victoria-metrics-windows-amd64
Makefile: add `release-victoria-metrics-arm64` build rule
2021-01-13 17:13:18 +01:00
Makefile: adds i386 architecture (#3725) see https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3661
2023-01-31 21:58:53 +01:00
release-victoria-metrics-linux-386:
GOOS=linux GOARCH=386 $(MAKE) release-victoria-metrics-goos-goarch
Rename release packages (#2810) * makefile: add os to each release file * makefile: update vmutils arm64 * makefile: update victoria-metrics release process * makefile: update publish with os * makefile: update publish with os * makefile: change tar library * update release logic * copy all releases * sort command by GOOS * rollback commands * rollback OSARCH * fix commands * cleanup * fix windows build * sort build by GOOS, update README.md
2022-07-13 14:42:48 +02:00
release-victoria-metrics-linux-amd64:
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
GOOS=linux GOARCH=amd64 $(MAKE) release-victoria-metrics-goos-goarch
adds release build for macos darwin amd64 and arm64 (#2185) * adds release build for macos darwin amd64 and arm64 https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1896 https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1851 * wip Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2022-02-14 16:28:56 +01:00
Rename release packages (#2810) * makefile: add os to each release file * makefile: update vmutils arm64 * makefile: update victoria-metrics release process * makefile: update publish with os * makefile: update publish with os * makefile: change tar library * update release logic * copy all releases * sort command by GOOS * rollback commands * rollback OSARCH * fix commands * cleanup * fix windows build * sort build by GOOS, update README.md
2022-07-13 14:42:48 +02:00
release-victoria-metrics-linux-arm:
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
GOOS=linux GOARCH=arm $(MAKE) release-victoria-metrics-goos-goarch
Rename release packages (#2810) * makefile: add os to each release file * makefile: update vmutils arm64 * makefile: update victoria-metrics release process * makefile: update publish with os * makefile: update publish with os * makefile: change tar library * update release logic * copy all releases * sort command by GOOS * rollback commands * rollback OSARCH * fix commands * cleanup * fix windows build * sort build by GOOS, update README.md
2022-07-13 14:42:48 +02:00
release-victoria-metrics-linux-arm64:
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
GOOS=linux GOARCH=arm64 $(MAKE) release-victoria-metrics-goos-goarch
release-victoria-metrics-darwin-amd64:
GOOS=darwin GOARCH=amd64 $(MAKE) release-victoria-metrics-goos-goarch
Rename release packages (#2810) * makefile: add os to each release file * makefile: update vmutils arm64 * makefile: update victoria-metrics release process * makefile: update publish with os * makefile: update publish with os * makefile: change tar library * update release logic * copy all releases * sort command by GOOS * rollback commands * rollback OSARCH * fix commands * cleanup * fix windows build * sort build by GOOS, update README.md
2022-07-13 14:42:48 +02:00
adds release build for macos darwin amd64 and arm64 (#2185) * adds release build for macos darwin amd64 and arm64 https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1896 https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1851 * wip Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2022-02-14 16:28:56 +01:00
release-victoria-metrics-darwin-arm64:
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
GOOS=darwin GOARCH=arm64 $(MAKE) release-victoria-metrics-goos-goarch
release-victoria-metrics-freebsd-amd64:
GOOS=freebsd GOARCH=amd64 $(MAKE) release-victoria-metrics-goos-goarch
adds release build for macos darwin amd64 and arm64 (#2185) * adds release build for macos darwin amd64 and arm64 https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1896 https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1851 * wip Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2022-02-14 16:28:56 +01:00
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
release-victoria-metrics-openbsd-amd64:
GOOS=openbsd GOARCH=amd64 $(MAKE) release-victoria-metrics-goos-goarch
all: add Windows build for VictoriaMetrics This commit changes background merge algorithm, so it becomes compatible with Windows file semantics. The previous algorithm for background merge: 1. Merge source parts into a destination part inside tmp directory. 2. Create a file in txn directory with instructions on how to atomically swap source parts with the destination part. 3. Perform instructions from the file. 4. Delete the file with instructions. This algorithm guarantees that either source parts or destination part is visible in the partition after unclean shutdown at any step above, since the remaining files with instructions is replayed on the next restart, after that the remaining contents of the tmp directory is deleted. Unfortunately this algorithm doesn't work under Windows because it disallows removing and moving files, which are in use. So the new algorithm for background merge has been implemented: 1. Merge source parts into a destination part inside the partition directory itself. E.g. now the partition directory may contain both complete and incomplete parts. 2. Atomically update the parts.json file with the new list of parts after the merge, e.g. remove the source parts from the list and add the destination part to the list before storing it to parts.json file. 3. Remove the source parts from disk when they are no longer used. This algorithm guarantees that either source parts or destination part is visible in the partition after unclean shutdown at any step above, since incomplete partitions from step 1 or old source parts from step 3 are removed on the next startup by inspecting parts.json file. This algorithm should work under Windows, since it doesn't remove or move files in use. This algorithm has also the following benefits: - It should work better for NFS. - It fits object storage semantics. The new algorithm changes data storage format, so it is impossible to downgrade to the previous versions of VictoriaMetrics after upgrading to this algorithm. Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3236 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3821 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/70
2023-03-19 09:36:05 +01:00
release-victoria-metrics-windows-amd64:
GOARCH=amd64 $(MAKE) release-victoria-metrics-windows-goarch
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
release-victoria-metrics-goos-goarch: victoria-metrics-$(GOOS)-$(GOARCH)-prod
Makefile: add `release-victoria-metrics-arm64` build rule
2021-01-13 17:13:18 +01:00
cd bin && \
make: reset permissions when creating release archive (#6846) ### Describe Your Changes Forcefully set permissions for release binaries to 1000:1000. This helps to avoid issues such as https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6788 on systems with limitations around UID:GID configuration. "1000" UID and GID is widely used by linux distributions for the first user in the system. ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com>
2024-08-21 11:25:13 +02:00
tar $(TAR_OWNERSHIP) --transform="flags=r;s|-$(GOOS)-$(GOARCH)||" -czf victoria-metrics-$(GOOS)-$(GOARCH)-$(PKG_TAG).tar.gz \
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
victoria-metrics-$(GOOS)-$(GOARCH)-prod \
&& sha256sum victoria-metrics-$(GOOS)-$(GOARCH)-$(PKG_TAG).tar.gz \
victoria-metrics-$(GOOS)-$(GOARCH)-prod \
| sed s/-$(GOOS)-$(GOARCH)-prod/-prod/ > victoria-metrics-$(GOOS)-$(GOARCH)-$(PKG_TAG)_checksums.txt
cd bin && rm -rf victoria-metrics-$(GOOS)-$(GOARCH)-prod
all: open-sourcing single-node version
2019-05-22 23:16:55 +02:00
all: add Windows build for VictoriaMetrics This commit changes background merge algorithm, so it becomes compatible with Windows file semantics. The previous algorithm for background merge: 1. Merge source parts into a destination part inside tmp directory. 2. Create a file in txn directory with instructions on how to atomically swap source parts with the destination part. 3. Perform instructions from the file. 4. Delete the file with instructions. This algorithm guarantees that either source parts or destination part is visible in the partition after unclean shutdown at any step above, since the remaining files with instructions is replayed on the next restart, after that the remaining contents of the tmp directory is deleted. Unfortunately this algorithm doesn't work under Windows because it disallows removing and moving files, which are in use. So the new algorithm for background merge has been implemented: 1. Merge source parts into a destination part inside the partition directory itself. E.g. now the partition directory may contain both complete and incomplete parts. 2. Atomically update the parts.json file with the new list of parts after the merge, e.g. remove the source parts from the list and add the destination part to the list before storing it to parts.json file. 3. Remove the source parts from disk when they are no longer used. This algorithm guarantees that either source parts or destination part is visible in the partition after unclean shutdown at any step above, since incomplete partitions from step 1 or old source parts from step 3 are removed on the next startup by inspecting parts.json file. This algorithm should work under Windows, since it doesn't remove or move files in use. This algorithm has also the following benefits: - It should work better for NFS. - It fits object storage semantics. The new algorithm changes data storage format, so it is impossible to downgrade to the previous versions of VictoriaMetrics after upgrading to this algorithm. Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3236 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3821 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/70
2023-03-19 09:36:05 +01:00
release-victoria-metrics-windows-goarch: victoria-metrics-windows-$(GOARCH)-prod
cd bin && \
zip victoria-metrics-windows-$(GOARCH)-$(PKG_TAG).zip \
victoria-metrics-windows-$(GOARCH)-prod.exe \
&& sha256sum victoria-metrics-windows-$(GOARCH)-$(PKG_TAG).zip \
victoria-metrics-windows-$(GOARCH)-prod.exe \
> victoria-metrics-windows-$(GOARCH)-$(PKG_TAG)_checksums.txt
cd bin && rm -rf \
victoria-metrics-windows-$(GOARCH)-prod.exe
app/vlogscli: add support for live tailing
2024-10-09 12:26:07 +02:00
release-victoria-logs-bundle: \
release-victoria-logs \
release-vlogscli
publish-victoria-logs-bundle: \
publish-victoria-logs \
publish-vlogscli
Makefile: speedup `release`, `publish` and `crossbuild` rules by using parallel make
2023-11-20 21:51:33 +01:00
release-victoria-logs:
$(MAKE_PARALLEL) release-victoria-logs-linux-386 \
release-victoria-logs-linux-amd64 \
release-victoria-logs-linux-arm \
release-victoria-logs-linux-arm64 \
release-victoria-logs-darwin-amd64 \
release-victoria-logs-darwin-arm64 \
release-victoria-logs-freebsd-amd64 \
release-victoria-logs-openbsd-amd64 \
release-victoria-logs-windows-amd64
app/victoria-logs: initial code release
2023-06-20 07:55:12 +02:00
release-victoria-logs-linux-386:
GOOS=linux GOARCH=386 $(MAKE) release-victoria-logs-goos-goarch
release-victoria-logs-linux-amd64:
GOOS=linux GOARCH=amd64 $(MAKE) release-victoria-logs-goos-goarch
release-victoria-logs-linux-arm:
GOOS=linux GOARCH=arm $(MAKE) release-victoria-logs-goos-goarch
release-victoria-logs-linux-arm64:
GOOS=linux GOARCH=arm64 $(MAKE) release-victoria-logs-goos-goarch
release-victoria-logs-darwin-amd64:
GOOS=darwin GOARCH=amd64 $(MAKE) release-victoria-logs-goos-goarch
release-victoria-logs-darwin-arm64:
GOOS=darwin GOARCH=arm64 $(MAKE) release-victoria-logs-goos-goarch
release-victoria-logs-freebsd-amd64:
GOOS=freebsd GOARCH=amd64 $(MAKE) release-victoria-logs-goos-goarch
release-victoria-logs-openbsd-amd64:
GOOS=openbsd GOARCH=amd64 $(MAKE) release-victoria-logs-goos-goarch
release-victoria-logs-windows-amd64:
GOARCH=amd64 $(MAKE) release-victoria-logs-windows-goarch
release-victoria-logs-goos-goarch: victoria-logs-$(GOOS)-$(GOARCH)-prod
cd bin && \
make: reset permissions when creating release archive (#6846) ### Describe Your Changes Forcefully set permissions for release binaries to 1000:1000. This helps to avoid issues such as https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6788 on systems with limitations around UID:GID configuration. "1000" UID and GID is widely used by linux distributions for the first user in the system. ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com>
2024-08-21 11:25:13 +02:00
tar $(TAR_OWNERSHIP) --transform="flags=r;s|-$(GOOS)-$(GOARCH)||" -czf victoria-logs-$(GOOS)-$(GOARCH)-$(PKG_TAG).tar.gz \
app/victoria-logs: initial code release
2023-06-20 07:55:12 +02:00
victoria-logs-$(GOOS)-$(GOARCH)-prod \
&& sha256sum victoria-logs-$(GOOS)-$(GOARCH)-$(PKG_TAG).tar.gz \
victoria-logs-$(GOOS)-$(GOARCH)-prod \
| sed s/-$(GOOS)-$(GOARCH)-prod/-prod/ > victoria-logs-$(GOOS)-$(GOARCH)-$(PKG_TAG)_checksums.txt
cd bin && rm -rf victoria-logs-$(GOOS)-$(GOARCH)-prod
release-victoria-logs-windows-goarch: victoria-logs-windows-$(GOARCH)-prod
cd bin && \
zip victoria-logs-windows-$(GOARCH)-$(PKG_TAG).zip \
victoria-logs-windows-$(GOARCH)-prod.exe \
&& sha256sum victoria-logs-windows-$(GOARCH)-$(PKG_TAG).zip \
victoria-logs-windows-$(GOARCH)-prod.exe \
> victoria-logs-windows-$(GOARCH)-$(PKG_TAG)_checksums.txt
cd bin && rm -rf \
victoria-logs-windows-$(GOARCH)-prod.exe
app/vlogscli: add interactive command-line tool for querying VictoriaLogs
2024-10-01 12:08:17 +02:00
release-vlogscli:
$(MAKE_PARALLEL) release-vlogscli-linux-386 \
release-vlogscli-linux-amd64 \
release-vlogscli-linux-arm \
release-vlogscli-linux-arm64 \
release-vlogscli-darwin-amd64 \
release-vlogscli-darwin-arm64 \
release-vlogscli-freebsd-amd64 \
release-vlogscli-openbsd-amd64 \
release-vlogscli-windows-amd64
release-vlogscli-linux-386:
GOOS=linux GOARCH=386 $(MAKE) release-vlogscli-goos-goarch
release-vlogscli-linux-amd64:
GOOS=linux GOARCH=amd64 $(MAKE) release-vlogscli-goos-goarch
release-vlogscli-linux-arm:
GOOS=linux GOARCH=arm $(MAKE) release-vlogscli-goos-goarch
release-vlogscli-linux-arm64:
GOOS=linux GOARCH=arm64 $(MAKE) release-vlogscli-goos-goarch
release-vlogscli-darwin-amd64:
GOOS=darwin GOARCH=amd64 $(MAKE) release-vlogscli-goos-goarch
release-vlogscli-darwin-arm64:
GOOS=darwin GOARCH=arm64 $(MAKE) release-vlogscli-goos-goarch
release-vlogscli-freebsd-amd64:
GOOS=freebsd GOARCH=amd64 $(MAKE) release-vlogscli-goos-goarch
release-vlogscli-openbsd-amd64:
GOOS=openbsd GOARCH=amd64 $(MAKE) release-vlogscli-goos-goarch
release-vlogscli-windows-amd64:
GOARCH=amd64 $(MAKE) release-vlogscli-windows-goarch
release-vlogscli-goos-goarch: vlogscli-$(GOOS)-$(GOARCH)-prod
cd bin && \
tar $(TAR_OWNERSHIP) --transform="flags=r;s|-$(GOOS)-$(GOARCH)||" -czf vlogscli-$(GOOS)-$(GOARCH)-$(PKG_TAG).tar.gz \
vlogscli-$(GOOS)-$(GOARCH)-prod \
&& sha256sum vlogscli-$(GOOS)-$(GOARCH)-$(PKG_TAG).tar.gz \
vlogscli-$(GOOS)-$(GOARCH)-prod \
| sed s/-$(GOOS)-$(GOARCH)-prod/-prod/ > vlogscli-$(GOOS)-$(GOARCH)-$(PKG_TAG)_checksums.txt
cd bin && rm -rf vlogscli-$(GOOS)-$(GOARCH)-prod
release-vlogscli-windows-goarch: vlogscli-windows-$(GOARCH)-prod
cd bin && \
zip vlogscli-windows-$(GOARCH)-$(PKG_TAG).zip \
vlogscli-windows-$(GOARCH)-prod.exe \
&& sha256sum vlogscli-windows-$(GOARCH)-$(PKG_TAG).zip \
vlogscli-windows-$(GOARCH)-prod.exe \
> vlogscli-windows-$(GOARCH)-$(PKG_TAG)_checksums.txt
cd bin && rm -rf \
vlogscli-windows-$(GOARCH)-prod.exe
Makefile: localize parallel make to `release`, `release-victoria-logs` and `crossbuild` commands This is a follow-up for 81ddee4f3ac85b6d97c3d9a57a4f3c3c343c76ca
2023-11-20 22:15:07 +01:00
release-vmutils: \
release-vmutils-linux-386 \
release-vmutils-linux-amd64 \
release-vmutils-linux-arm64 \
release-vmutils-linux-arm \
release-vmutils-darwin-amd64 \
release-vmutils-darwin-arm64 \
release-vmutils-freebsd-amd64 \
release-vmutils-openbsd-amd64 \
release-vmutils-windows-amd64
Makefile: release vmutils for amd64 and arm64 Follow-up for 0d03855787d526e51980e5935d9a59c83f92f143
2021-01-13 17:02:28 +01:00
Makefile: adds i386 architecture (#3725) see https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3661
2023-01-31 21:58:53 +01:00
release-vmutils-linux-386:
GOOS=linux GOARCH=386 $(MAKE) release-vmutils-goos-goarch
testing: allow disabling fsync to make tests run faster (#6871) ### Describe Your Changes fsync() ensures that the data is written to disk. In production this is needed for data durability. However, during the development, when the unit tests are run, this level of durability is not needed. Therefore fsync() can be disabled which will makes test runs two times faster. The disabling is done by setting the `DISABLE_FSYNC_FOR_TESTING` environment variable. The valid values for this variable are the same as the values of the arg of `go doc strconv.ParseBool`: ``` 1, t, T, TRUE, true, True, 0, f, F, FALSE, false, False. ``` Any other value means `false`. The variable is set for all test build targets. Compare running times: Build Target | DISABLE_FSYNC_FOR_TESTING=0 | DISABLE_FSYNC_FOR_TESTING=1 ----------------- | ------------------------------------------------ | ------------------------------------------------- make test | 1m5s | 0m22s make test-race | 3m1s | 1m42s make test-pure | 1m7s | 0m20s make test-full | 1m21s | 0m32s make test-full-386 | 1m42s | 0m36s When running tests for a given package, fsync can be disabled as follows: ```shell DISABLE_FSYNC_FOR_TESTING=1 go test ./lib/storage ``` Disabling fsync() is intended for testing purposes only and the name of the variables reflects that. What could also have been done but haven't: - lib/filestream/filestream.go: `Writer.MustFlush()` also uses f.Sync() but nothing has been done to it, because the Writer.MustFlush() is not used anywhere in the VM codebase. A side question: what is the general policy for the unused code? - lib/filestream/filestream.go: Writer.Write() calls `adviceDontNeed()` which calls unix.Fdatasync(). Disabling it could potentially improve running time, but running tests with this code disabled has shown otherwise. ### Checklist The following checks are **mandatory**: - [ x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <wwctrsrx@gmail.com>
2024-08-30 10:54:46 +02:00
Rename release packages (#2810) * makefile: add os to each release file * makefile: update vmutils arm64 * makefile: update victoria-metrics release process * makefile: update publish with os * makefile: update publish with os * makefile: change tar library * update release logic * copy all releases * sort command by GOOS * rollback commands * rollback OSARCH * fix commands * cleanup * fix windows build * sort build by GOOS, update README.md
2022-07-13 14:42:48 +02:00
release-vmutils-linux-amd64:
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
GOOS=linux GOARCH=amd64 $(MAKE) release-vmutils-goos-goarch
adds release build for macos darwin amd64 and arm64 (#2185) * adds release build for macos darwin amd64 and arm64 https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1896 https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1851 * wip Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2022-02-14 16:28:56 +01:00
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
release-vmutils-linux-arm64:
GOOS=linux GOARCH=arm64 $(MAKE) release-vmutils-goos-goarch
Makefile: prepare vmutils-windows-*.zip archive on `make release-vmutils` command The archive contains the following executables for Windows: * vmagent * vmalert * vmauth * vmctl Other components - vmbackup, vmrestore, victoria-metrics - aren't supported for Windows yet
2021-03-16 19:49:07 +01:00
Rename release packages (#2810) * makefile: add os to each release file * makefile: update vmutils arm64 * makefile: update victoria-metrics release process * makefile: update publish with os * makefile: update publish with os * makefile: change tar library * update release logic * copy all releases * sort command by GOOS * rollback commands * rollback OSARCH * fix commands * cleanup * fix windows build * sort build by GOOS, update README.md
2022-07-13 14:42:48 +02:00
release-vmutils-linux-arm:
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
GOOS=linux GOARCH=arm $(MAKE) release-vmutils-goos-goarch
Rename release packages (#2810) * makefile: add os to each release file * makefile: update vmutils arm64 * makefile: update victoria-metrics release process * makefile: update publish with os * makefile: update publish with os * makefile: change tar library * update release logic * copy all releases * sort command by GOOS * rollback commands * rollback OSARCH * fix commands * cleanup * fix windows build * sort build by GOOS, update README.md
2022-07-13 14:42:48 +02:00
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
release-vmutils-darwin-amd64:
GOOS=darwin GOARCH=amd64 $(MAKE) release-vmutils-goos-goarch
Rename release packages (#2810) * makefile: add os to each release file * makefile: update vmutils arm64 * makefile: update victoria-metrics release process * makefile: update publish with os * makefile: update publish with os * makefile: change tar library * update release logic * copy all releases * sort command by GOOS * rollback commands * rollback OSARCH * fix commands * cleanup * fix windows build * sort build by GOOS, update README.md
2022-07-13 14:42:48 +02:00
release-vmutils-darwin-arm64:
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
GOOS=darwin GOARCH=arm64 $(MAKE) release-vmutils-goos-goarch
release-vmutils-freebsd-amd64:
GOOS=freebsd GOARCH=amd64 $(MAKE) release-vmutils-goos-goarch
release-vmutils-openbsd-amd64:
GOOS=openbsd GOARCH=amd64 $(MAKE) release-vmutils-goos-goarch
release-vmutils-windows-amd64:
GOARCH=amd64 $(MAKE) release-vmutils-windows-goarch
release-vmutils-goos-goarch: \
vmagent-$(GOOS)-$(GOARCH)-prod \
vmalert-$(GOOS)-$(GOARCH)-prod \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
vmalert-tool-$(GOOS)-$(GOARCH)-prod \
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
vmauth-$(GOOS)-$(GOARCH)-prod \
vmbackup-$(GOOS)-$(GOARCH)-prod \
vmrestore-$(GOOS)-$(GOARCH)-prod \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
vmctl-$(GOOS)-$(GOARCH)-prod
Arch consistent filenames (#1015) * Include individual binary checksums for vmutils * Consistent archive/binary artefacts between arm64/amd64 for vmutils * architecture in arhcive, checksums * not in binaries
2021-01-13 16:31:08 +01:00
cd bin && \
make: reset permissions when creating release archive (#6846) ### Describe Your Changes Forcefully set permissions for release binaries to 1000:1000. This helps to avoid issues such as https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6788 on systems with limitations around UID:GID configuration. "1000" UID and GID is widely used by linux distributions for the first user in the system. ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com>
2024-08-21 11:25:13 +02:00
tar $(TAR_OWNERSHIP) --transform="flags=r;s|-$(GOOS)-$(GOARCH)||" -czf vmutils-$(GOOS)-$(GOARCH)-$(PKG_TAG).tar.gz \
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
vmagent-$(GOOS)-$(GOARCH)-prod \
vmalert-$(GOOS)-$(GOARCH)-prod \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
vmalert-tool-$(GOOS)-$(GOARCH)-prod \
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
vmauth-$(GOOS)-$(GOARCH)-prod \
vmbackup-$(GOOS)-$(GOARCH)-prod \
vmrestore-$(GOOS)-$(GOARCH)-prod \
vmctl-$(GOOS)-$(GOARCH)-prod \
&& sha256sum vmutils-$(GOOS)-$(GOARCH)-$(PKG_TAG).tar.gz \
vmagent-$(GOOS)-$(GOARCH)-prod \
vmalert-$(GOOS)-$(GOARCH)-prod \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
vmalert-tool-$(GOOS)-$(GOARCH)-prod \
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
vmauth-$(GOOS)-$(GOARCH)-prod \
vmbackup-$(GOOS)-$(GOARCH)-prod \
vmrestore-$(GOOS)-$(GOARCH)-prod \
vmctl-$(GOOS)-$(GOARCH)-prod \
| sed s/-$(GOOS)-$(GOARCH)-prod/-prod/ > vmutils-$(GOOS)-$(GOARCH)-$(PKG_TAG)_checksums.txt
cd bin && rm -rf \
vmagent-$(GOOS)-$(GOARCH)-prod \
vmalert-$(GOOS)-$(GOARCH)-prod \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
vmalert-tool-$(GOOS)-$(GOARCH)-prod \
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
vmauth-$(GOOS)-$(GOARCH)-prod \
vmbackup-$(GOOS)-$(GOARCH)-prod \
vmrestore-$(GOOS)-$(GOARCH)-prod \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
vmctl-$(GOOS)-$(GOARCH)-prod
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
release-vmutils-windows-goarch: \
Makefile: prepare vmutils-windows-*.zip archive on `make release-vmutils` command The archive contains the following executables for Windows: * vmagent * vmalert * vmauth * vmctl Other components - vmbackup, vmrestore, victoria-metrics - aren't supported for Windows yet
2021-03-16 19:49:07 +01:00
vmagent-windows-$(GOARCH)-prod \
vmalert-windows-$(GOARCH)-prod \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
vmalert-tool-windows-$(GOARCH)-prod \
Makefile: prepare vmutils-windows-*.zip archive on `make release-vmutils` command The archive contains the following executables for Windows: * vmagent * vmalert * vmauth * vmctl Other components - vmbackup, vmrestore, victoria-metrics - aren't supported for Windows yet
2021-03-16 19:49:07 +01:00
vmauth-windows-$(GOARCH)-prod \
app/{vmbackup,vmrestore}: publish vmbackup and vmrestore binaries for Windows Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/70
2023-03-25 23:08:12 +01:00
vmbackup-windows-$(GOARCH)-prod \
vmrestore-windows-$(GOARCH)-prod \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
vmctl-windows-$(GOARCH)-prod
Makefile: prepare vmutils-windows-*.zip archive on `make release-vmutils` command The archive contains the following executables for Windows: * vmagent * vmalert * vmauth * vmctl Other components - vmbackup, vmrestore, victoria-metrics - aren't supported for Windows yet
2021-03-16 19:49:07 +01:00
cd bin && \
zip vmutils-windows-$(GOARCH)-$(PKG_TAG).zip \
vmagent-windows-$(GOARCH)-prod.exe \
vmalert-windows-$(GOARCH)-prod.exe \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
vmalert-tool-windows-$(GOARCH)-prod.exe \
Makefile: prepare vmutils-windows-*.zip archive on `make release-vmutils` command The archive contains the following executables for Windows: * vmagent * vmalert * vmauth * vmctl Other components - vmbackup, vmrestore, victoria-metrics - aren't supported for Windows yet
2021-03-16 19:49:07 +01:00
vmauth-windows-$(GOARCH)-prod.exe \
app/{vmbackup,vmrestore}: publish vmbackup and vmrestore binaries for Windows Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/70
2023-03-25 23:08:12 +01:00
vmbackup-windows-$(GOARCH)-prod.exe \
vmrestore-windows-$(GOARCH)-prod.exe \
Makefile: prepare vmutils-windows-*.zip archive on `make release-vmutils` command The archive contains the following executables for Windows: * vmagent * vmalert * vmauth * vmctl Other components - vmbackup, vmrestore, victoria-metrics - aren't supported for Windows yet
2021-03-16 19:49:07 +01:00
vmctl-windows-$(GOARCH)-prod.exe \
&& sha256sum vmutils-windows-$(GOARCH)-$(PKG_TAG).zip \
vmagent-windows-$(GOARCH)-prod.exe \
vmalert-windows-$(GOARCH)-prod.exe \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
vmalert-tool-windows-$(GOARCH)-prod.exe \
Makefile: prepare vmutils-windows-*.zip archive on `make release-vmutils` command The archive contains the following executables for Windows: * vmagent * vmalert * vmauth * vmctl Other components - vmbackup, vmrestore, victoria-metrics - aren't supported for Windows yet
2021-03-16 19:49:07 +01:00
vmauth-windows-$(GOARCH)-prod.exe \
app/{vmbackup,vmrestore}: publish vmbackup and vmrestore binaries for Windows Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/70
2023-03-25 23:08:12 +01:00
vmbackup-windows-$(GOARCH)-prod.exe \
vmrestore-windows-$(GOARCH)-prod.exe \
Makefile: prepare vmutils-windows-*.zip archive on `make release-vmutils` command The archive contains the following executables for Windows: * vmagent * vmalert * vmauth * vmctl Other components - vmbackup, vmrestore, victoria-metrics - aren't supported for Windows yet
2021-03-16 19:49:07 +01:00
vmctl-windows-$(GOARCH)-prod.exe \
> vmutils-windows-$(GOARCH)-$(PKG_TAG)_checksums.txt
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
cd bin && rm -rf \
vmagent-windows-$(GOARCH)-prod.exe \
vmalert-windows-$(GOARCH)-prod.exe \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
vmalert-tool-windows-$(GOARCH)-prod.exe \
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
vmauth-windows-$(GOARCH)-prod.exe \
app/{vmbackup,vmrestore}: publish vmbackup and vmrestore binaries for Windows Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/70
2023-03-25 23:08:12 +01:00
vmbackup-windows-$(GOARCH)-prod.exe \
vmrestore-windows-$(GOARCH)-prod.exe \
Makefile: move build commands for vmalert-tool closer to vmalert This should simplify maintenance of Makefile commands related to vmalert. This is a follow-up for dc28196237b7a3ceb16a49b0a0a8dd077634b5ab
2023-10-26 08:06:35 +02:00
vmctl-windows-$(GOARCH)-prod.exe
Makefile: prepare vmutils-windows-*.zip archive on `make release-vmutils` command The archive contains the following executables for Windows: * vmagent * vmalert * vmauth * vmctl Other components - vmbackup, vmrestore, victoria-metrics - aren't supported for Windows yet
2021-03-16 19:49:07 +01:00
Makefile: add `pprof-cpu` rule for inspecting CPU profiles with `PPROF_FILE=/path/to/cpu.pprof make pprof-cpu`
2019-11-04 11:43:26 +01:00
pprof-cpu:
go tool pprof -trim_path=github.com/VictoriaMetrics/VictoriaMetrics@ $(PPROF_FILE)
all: open-sourcing single-node version
2019-05-22 23:16:55 +02:00
fmt:
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
gofmt -l -w -s ./lib
gofmt -l -w -s ./app
tests: Initial version of integration tests (#7253) ### Describe Your Changes Related issue: #7199 This is the initial version of the integration tests for cluster. See `README.md` for details. Currently cluster only, but it can also be used for vm-single if needed. The code has been added to the apptest package that resides in the root directory of the VM codebase. This is done to exclude the integration tests from regular testing build targets because: - Most of the test variants do not apply to integration testing (such as pure or race). - The integtation tests may also be slow because each test must wait for 2 seconds so vmstorage flushes pending content). It may be okay when there are a few tests but when there is a 100 of them running tests will require much more time which will affect the developer wait time and CI workflows. - Finally, the integration tests may be flaky especially short term. An alternative approach would be placing apptest under app package and exclude apptest from packages under test, but that is not trivial. The integration tests rely on retrieving some application runtime info from the application logs, namely the application's host:port. Therefore some changes to lib/httpserver/httpserver.go were necessary, such as reporting the effective host:port instead the one from the flag. ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> (cherry picked from commit d7b3589dbd0a3f38cecf7f8e896a3686c0dd8d4c)
2024-10-30 15:22:06 +01:00
gofmt -l -w -s ./apptest
all: open-sourcing single-node version
2019-05-22 23:16:55 +02:00
vet:
Makefile: remove redundant `-mod=vendor` option when running Go tools The `-mod=vendor` is automatically set when there is a `vendor` directory starting from Go1.14 - see https://go.dev/doc/go1.14#go-command Since the minimum supported Go version for VictoriaMetrics is Go1.17, then the `-mod=vendor` option is no longer needed.
2022-08-07 19:39:05 +02:00
go vet ./lib/...
go vet ./app/...
tests: Initial version of integration tests (#7253) ### Describe Your Changes Related issue: #7199 This is the initial version of the integration tests for cluster. See `README.md` for details. Currently cluster only, but it can also be used for vm-single if needed. The code has been added to the apptest package that resides in the root directory of the VM codebase. This is done to exclude the integration tests from regular testing build targets because: - Most of the test variants do not apply to integration testing (such as pure or race). - The integtation tests may also be slow because each test must wait for 2 seconds so vmstorage flushes pending content). It may be okay when there are a few tests but when there is a 100 of them running tests will require much more time which will affect the developer wait time and CI workflows. - Finally, the integration tests may be flaky especially short term. An alternative approach would be placing apptest under app package and exclude apptest from packages under test, but that is not trivial. The integration tests rely on retrieving some application runtime info from the application logs, namely the application's host:port. Therefore some changes to lib/httpserver/httpserver.go were necessary, such as reporting the effective host:port instead the one from the flag. ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> (cherry picked from commit d7b3589dbd0a3f38cecf7f8e896a3686c0dd8d4c)
2024-10-30 15:22:06 +01:00
go vet ./apptest/...
all: open-sourcing single-node version
2019-05-22 23:16:55 +02:00
Revert "make: add goimports task (#4582)" This reverts commit 20b18e9feb71e91b3075bba74b245e5b35a4e5c8. Reason for revert: running goimports on `make check-all` introduces the following issues: - It runs only on modified files, which weren't commited yet into git repository. This means the formatting for the remaining files becomes different comparing to the formatting for the changed files. This also means that the goimports has no any effect at github actions and when the changed code is already commited to git repository. - `gomiports` performs formatting in the same way as gofmt, so `make fmt` becomes unnecessary. But when `gofmt` is substituted with `goimports`, then it performs unnecessary formatting for *.qtpl.go files. It is possible to make a hack, which will prepare a list of all the *.go files at lib/ and app/ without the *.qtpl.go files, and then feed this list to `goimports`, but this looks too fragile for the task of just fixing the ordering of Go imports. So it is better to leave source code formatting as is with `gofmt`, while manually fixing improper ordering of Go import from time to time in dedicated commits until better solution arises.
2023-07-13 20:51:56 +02:00
check-all: fmt vet golangci-lint govulncheck
[ci-ci] enable CI (#39)
2019-05-29 00:32:49 +02:00
Makefile: add `clean-checkers` rule for dropping checker apps used in `make check-all` The `make clean-checkers` command may be useful when the locally installed checker apps are too old, so they must be updated to the newly requested versions by `make check-all`. In this case the fix is to run make clean-checkers check-all
2024-06-25 20:28:38 +02:00
clean-checkers: remove-golangci-lint remove-govulncheck
all: open-sourcing single-node version
2019-05-22 23:16:55 +02:00
test:
testing: allow disabling fsync to make tests run faster (#6871) ### Describe Your Changes fsync() ensures that the data is written to disk. In production this is needed for data durability. However, during the development, when the unit tests are run, this level of durability is not needed. Therefore fsync() can be disabled which will makes test runs two times faster. The disabling is done by setting the `DISABLE_FSYNC_FOR_TESTING` environment variable. The valid values for this variable are the same as the values of the arg of `go doc strconv.ParseBool`: ``` 1, t, T, TRUE, true, True, 0, f, F, FALSE, false, False. ``` Any other value means `false`. The variable is set for all test build targets. Compare running times: Build Target | DISABLE_FSYNC_FOR_TESTING=0 | DISABLE_FSYNC_FOR_TESTING=1 ----------------- | ------------------------------------------------ | ------------------------------------------------- make test | 1m5s | 0m22s make test-race | 3m1s | 1m42s make test-pure | 1m7s | 0m20s make test-full | 1m21s | 0m32s make test-full-386 | 1m42s | 0m36s When running tests for a given package, fsync can be disabled as follows: ```shell DISABLE_FSYNC_FOR_TESTING=1 go test ./lib/storage ``` Disabling fsync() is intended for testing purposes only and the name of the variables reflects that. What could also have been done but haven't: - lib/filestream/filestream.go: `Writer.MustFlush()` also uses f.Sync() but nothing has been done to it, because the Writer.MustFlush() is not used anywhere in the VM codebase. A side question: what is the general policy for the unused code? - lib/filestream/filestream.go: Writer.Write() calls `adviceDontNeed()` which calls unix.Fdatasync(). Disabling it could potentially improve running time, but running tests with this code disabled has shown otherwise. ### Checklist The following checks are **mandatory**: - [ x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <wwctrsrx@gmail.com>
2024-08-30 10:54:46 +02:00
DISABLE_FSYNC_FOR_TESTING=1 go test ./lib/... ./app/...
[ci-ci] enable CI (#39)
2019-05-29 00:32:49 +02:00
Makefile: add build and test rules with enabled race detector. These rules have `-race` suffix Fix also `unsafe pointer conversion` errors detected by Go1.14. See https://golang.org/doc/go1.14#compiler .
2020-03-05 11:02:06 +01:00
test-race:
testing: allow disabling fsync to make tests run faster (#6871) ### Describe Your Changes fsync() ensures that the data is written to disk. In production this is needed for data durability. However, during the development, when the unit tests are run, this level of durability is not needed. Therefore fsync() can be disabled which will makes test runs two times faster. The disabling is done by setting the `DISABLE_FSYNC_FOR_TESTING` environment variable. The valid values for this variable are the same as the values of the arg of `go doc strconv.ParseBool`: ``` 1, t, T, TRUE, true, True, 0, f, F, FALSE, false, False. ``` Any other value means `false`. The variable is set for all test build targets. Compare running times: Build Target | DISABLE_FSYNC_FOR_TESTING=0 | DISABLE_FSYNC_FOR_TESTING=1 ----------------- | ------------------------------------------------ | ------------------------------------------------- make test | 1m5s | 0m22s make test-race | 3m1s | 1m42s make test-pure | 1m7s | 0m20s make test-full | 1m21s | 0m32s make test-full-386 | 1m42s | 0m36s When running tests for a given package, fsync can be disabled as follows: ```shell DISABLE_FSYNC_FOR_TESTING=1 go test ./lib/storage ``` Disabling fsync() is intended for testing purposes only and the name of the variables reflects that. What could also have been done but haven't: - lib/filestream/filestream.go: `Writer.MustFlush()` also uses f.Sync() but nothing has been done to it, because the Writer.MustFlush() is not used anywhere in the VM codebase. A side question: what is the general policy for the unused code? - lib/filestream/filestream.go: Writer.Write() calls `adviceDontNeed()` which calls unix.Fdatasync(). Disabling it could potentially improve running time, but running tests with this code disabled has shown otherwise. ### Checklist The following checks are **mandatory**: - [ x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <wwctrsrx@gmail.com>
2024-08-30 10:54:46 +02:00
DISABLE_FSYNC_FOR_TESTING=1 go test -race ./lib/... ./app/...
Makefile: add build and test rules with enabled race detector. These rules have `-race` suffix Fix also `unsafe pointer conversion` errors detected by Go1.14. See https://golang.org/doc/go1.14#compiler .
2020-03-05 11:02:06 +01:00
all: add Pure Go build (pull request #114) Updates #94
2019-07-23 18:26:39 +02:00
test-pure:
testing: allow disabling fsync to make tests run faster (#6871) ### Describe Your Changes fsync() ensures that the data is written to disk. In production this is needed for data durability. However, during the development, when the unit tests are run, this level of durability is not needed. Therefore fsync() can be disabled which will makes test runs two times faster. The disabling is done by setting the `DISABLE_FSYNC_FOR_TESTING` environment variable. The valid values for this variable are the same as the values of the arg of `go doc strconv.ParseBool`: ``` 1, t, T, TRUE, true, True, 0, f, F, FALSE, false, False. ``` Any other value means `false`. The variable is set for all test build targets. Compare running times: Build Target | DISABLE_FSYNC_FOR_TESTING=0 | DISABLE_FSYNC_FOR_TESTING=1 ----------------- | ------------------------------------------------ | ------------------------------------------------- make test | 1m5s | 0m22s make test-race | 3m1s | 1m42s make test-pure | 1m7s | 0m20s make test-full | 1m21s | 0m32s make test-full-386 | 1m42s | 0m36s When running tests for a given package, fsync can be disabled as follows: ```shell DISABLE_FSYNC_FOR_TESTING=1 go test ./lib/storage ``` Disabling fsync() is intended for testing purposes only and the name of the variables reflects that. What could also have been done but haven't: - lib/filestream/filestream.go: `Writer.MustFlush()` also uses f.Sync() but nothing has been done to it, because the Writer.MustFlush() is not used anywhere in the VM codebase. A side question: what is the general policy for the unused code? - lib/filestream/filestream.go: Writer.Write() calls `adviceDontNeed()` which calls unix.Fdatasync(). Disabling it could potentially improve running time, but running tests with this code disabled has shown otherwise. ### Checklist The following checks are **mandatory**: - [ x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <wwctrsrx@gmail.com>
2024-08-30 10:54:46 +02:00
DISABLE_FSYNC_FOR_TESTING=1 CGO_ENABLED=0 go test ./lib/... ./app/...
all: small updates after PR #114
2019-07-23 18:54:50 +02:00
test-full:
testing: allow disabling fsync to make tests run faster (#6871) ### Describe Your Changes fsync() ensures that the data is written to disk. In production this is needed for data durability. However, during the development, when the unit tests are run, this level of durability is not needed. Therefore fsync() can be disabled which will makes test runs two times faster. The disabling is done by setting the `DISABLE_FSYNC_FOR_TESTING` environment variable. The valid values for this variable are the same as the values of the arg of `go doc strconv.ParseBool`: ``` 1, t, T, TRUE, true, True, 0, f, F, FALSE, false, False. ``` Any other value means `false`. The variable is set for all test build targets. Compare running times: Build Target | DISABLE_FSYNC_FOR_TESTING=0 | DISABLE_FSYNC_FOR_TESTING=1 ----------------- | ------------------------------------------------ | ------------------------------------------------- make test | 1m5s | 0m22s make test-race | 3m1s | 1m42s make test-pure | 1m7s | 0m20s make test-full | 1m21s | 0m32s make test-full-386 | 1m42s | 0m36s When running tests for a given package, fsync can be disabled as follows: ```shell DISABLE_FSYNC_FOR_TESTING=1 go test ./lib/storage ``` Disabling fsync() is intended for testing purposes only and the name of the variables reflects that. What could also have been done but haven't: - lib/filestream/filestream.go: `Writer.MustFlush()` also uses f.Sync() but nothing has been done to it, because the Writer.MustFlush() is not used anywhere in the VM codebase. A side question: what is the general policy for the unused code? - lib/filestream/filestream.go: Writer.Write() calls `adviceDontNeed()` which calls unix.Fdatasync(). Disabling it could potentially improve running time, but running tests with this code disabled has shown otherwise. ### Checklist The following checks are **mandatory**: - [ x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <wwctrsrx@gmail.com>
2024-08-30 10:54:46 +02:00
DISABLE_FSYNC_FOR_TESTING=1 go test -coverprofile=coverage.txt -covermode=atomic ./lib/... ./app/...
all: add Pure Go build (pull request #114) Updates #94
2019-07-23 18:26:39 +02:00
all: add support for GOARCH=386 and fix all the issues related to 32-bit architectures such as GOARCH=arm Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/212
2019-10-17 17:22:56 +02:00
test-full-386:
testing: allow disabling fsync to make tests run faster (#6871) ### Describe Your Changes fsync() ensures that the data is written to disk. In production this is needed for data durability. However, during the development, when the unit tests are run, this level of durability is not needed. Therefore fsync() can be disabled which will makes test runs two times faster. The disabling is done by setting the `DISABLE_FSYNC_FOR_TESTING` environment variable. The valid values for this variable are the same as the values of the arg of `go doc strconv.ParseBool`: ``` 1, t, T, TRUE, true, True, 0, f, F, FALSE, false, False. ``` Any other value means `false`. The variable is set for all test build targets. Compare running times: Build Target | DISABLE_FSYNC_FOR_TESTING=0 | DISABLE_FSYNC_FOR_TESTING=1 ----------------- | ------------------------------------------------ | ------------------------------------------------- make test | 1m5s | 0m22s make test-race | 3m1s | 1m42s make test-pure | 1m7s | 0m20s make test-full | 1m21s | 0m32s make test-full-386 | 1m42s | 0m36s When running tests for a given package, fsync can be disabled as follows: ```shell DISABLE_FSYNC_FOR_TESTING=1 go test ./lib/storage ``` Disabling fsync() is intended for testing purposes only and the name of the variables reflects that. What could also have been done but haven't: - lib/filestream/filestream.go: `Writer.MustFlush()` also uses f.Sync() but nothing has been done to it, because the Writer.MustFlush() is not used anywhere in the VM codebase. A side question: what is the general policy for the unused code? - lib/filestream/filestream.go: Writer.Write() calls `adviceDontNeed()` which calls unix.Fdatasync(). Disabling it could potentially improve running time, but running tests with this code disabled has shown otherwise. ### Checklist The following checks are **mandatory**: - [ x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <wwctrsrx@gmail.com>
2024-08-30 10:54:46 +02:00
DISABLE_FSYNC_FOR_TESTING=1 GOARCH=386 go test -coverprofile=coverage.txt -covermode=atomic ./lib/... ./app/...
all: add support for GOARCH=386 and fix all the issues related to 32-bit architectures such as GOARCH=arm Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/212
2019-10-17 17:22:56 +02:00
tests: integration tests for vmsingle (#7434) ### Describe Your Changes This PR continues the implementation of integration tests (#7199). It adds the support for vm-single: - A vmsingle app wrapper has been added - Sample vmsingle tests that test the VM documentation related to querying data (#7435) - The tests use the go-cmp/{cmp,/cmpopts} packages, therefore they have been added to ./vendor - Minor refactoring: data objects have been moved to model.go Advice on porting things to cluster branch: - The build rule must include tests that start with TestVmsingle (similarly to how TestCluster tests are skipped in master branch) - The build rule must depend on `vmstorage vminsert vmselect` instead of `victoria-metrics` - The query_test.go can actually be implemented for cluster as well. To do this the tests need to be renamed to start with TestCluster and the tests must instantiace vm{storage,insert,select} instead of vmsingle. ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com>
2024-11-07 12:58:37 +01:00
integration-test: victoria-metrics vmagent vmalert vmauth
apptest: typical cluster configuration for business logic tests Add the ability to create a simple cluster configuration for tests that do not verify the cluster-specific behavior but instead are focused on the business logic tests, such as API surface or MetricsQL. For such tests this cluster configuration will be enough in most cases. Cluster-specific tests should continue creating custom configurations. --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com>
2024-11-20 16:30:55 +01:00
go test ./apptest/... -skip="^TestCluster.*" -v
tests: Initial version of integration tests (#7253) ### Describe Your Changes Related issue: #7199 This is the initial version of the integration tests for cluster. See `README.md` for details. Currently cluster only, but it can also be used for vm-single if needed. The code has been added to the apptest package that resides in the root directory of the VM codebase. This is done to exclude the integration tests from regular testing build targets because: - Most of the test variants do not apply to integration testing (such as pure or race). - The integtation tests may also be slow because each test must wait for 2 seconds so vmstorage flushes pending content). It may be okay when there are a few tests but when there is a 100 of them running tests will require much more time which will affect the developer wait time and CI workflows. - Finally, the integration tests may be flaky especially short term. An alternative approach would be placing apptest under app package and exclude apptest from packages under test, but that is not trivial. The integration tests rely on retrieving some application runtime info from the application logs, namely the application's host:port. Therefore some changes to lib/httpserver/httpserver.go were necessary, such as reporting the effective host:port instead the one from the flag. ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> (cherry picked from commit d7b3589dbd0a3f38cecf7f8e896a3686c0dd8d4c)
2024-10-30 15:22:06 +01:00
all: open-sourcing single-node version
2019-05-22 23:16:55 +02:00
benchmark:
Makefile: remove redundant `-mod=vendor` option when running Go tools The `-mod=vendor` is automatically set when there is a `vendor` directory starting from Go1.14 - see https://go.dev/doc/go1.14#go-command Since the minimum supported Go version for VictoriaMetrics is Go1.17, then the `-mod=vendor` option is no longer needed.
2022-08-07 19:39:05 +02:00
go test -bench=. ./lib/...
go test -bench=. ./app/...
all: open-sourcing single-node version
2019-05-22 23:16:55 +02:00
all: add Pure Go build (pull request #114) Updates #94
2019-07-23 18:26:39 +02:00
benchmark-pure:
Makefile: remove redundant `-mod=vendor` option when running Go tools The `-mod=vendor` is automatically set when there is a `vendor` directory starting from Go1.14 - see https://go.dev/doc/go1.14#go-command Since the minimum supported Go version for VictoriaMetrics is Go1.17, then the `-mod=vendor` option is no longer needed.
2022-08-07 19:39:05 +02:00
CGO_ENABLED=0 go test -bench=. ./lib/...
CGO_ENABLED=0 go test -bench=. ./app/...
all: add Pure Go build (pull request #114) Updates #94
2019-07-23 18:26:39 +02:00
all: open-sourcing single-node version
2019-05-22 23:16:55 +02:00
vendor-update:
Makefile: remove '-d' flag from 'go get', since this flag is deprecated See https://go.dev/doc/go-get-install-deprecation
2024-09-08 20:06:30 +02:00
go get -u ./lib/...
go get -u ./app/...
Makefile: upgrade `go mod tidy` compatibility mode from Go1.22 to Go1.23 This is a follow-up for 1b9f3b39b4b2026b3e9cdac8c25f194c0ef472f1
2024-09-08 21:01:15 +02:00
go mod tidy -compat=1.23
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
go mod vendor
all: open-sourcing single-node version
2019-05-22 23:16:55 +02:00
Makefile: extract `app-local` and `app-local-pure` build rules
2019-08-28 00:34:26 +02:00
app-local:
Makefile: remove redundant `-mod=vendor` option when running Go tools The `-mod=vendor` is automatically set when there is a `vendor` directory starting from Go1.14 - see https://go.dev/doc/go1.14#go-command Since the minimum supported Go version for VictoriaMetrics is Go1.17, then the `-mod=vendor` option is no longer needed.
2022-08-07 19:39:05 +02:00
CGO_ENABLED=1 go build $(RACE) -ldflags "$(GO_BUILDINFO)" -o bin/$(APP_NAME)$(RACE) $(PKG_PREFIX)/app/$(APP_NAME)
Makefile: extract `app-local` and `app-local-pure` build rules
2019-08-28 00:34:26 +02:00
app-local-pure:
Makefile: remove redundant `-mod=vendor` option when running Go tools The `-mod=vendor` is automatically set when there is a `vendor` directory starting from Go1.14 - see https://go.dev/doc/go1.14#go-command Since the minimum supported Go version for VictoriaMetrics is Go1.17, then the `-mod=vendor` option is no longer needed.
2022-08-07 19:39:05 +02:00
CGO_ENABLED=0 go build $(RACE) -ldflags "$(GO_BUILDINFO)" -o bin/$(APP_NAME)-pure$(RACE) $(PKG_PREFIX)/app/$(APP_NAME)
Makefile: extract `app-local` and `app-local-pure` build rules
2019-08-28 00:34:26 +02:00
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
app-local-goos-goarch:
Makefile: remove redundant `-mod=vendor` option when running Go tools The `-mod=vendor` is automatically set when there is a `vendor` directory starting from Go1.14 - see https://go.dev/doc/go1.14#go-command Since the minimum supported Go version for VictoriaMetrics is Go1.17, then the `-mod=vendor` option is no longer needed.
2022-08-07 19:39:05 +02:00
CGO_ENABLED=$(CGO_ENABLED) GOOS=$(GOOS) GOARCH=$(GOARCH) go build $(RACE) -ldflags "$(GO_BUILDINFO)" -o bin/$(APP_NAME)-$(GOOS)-$(GOARCH)$(RACE) $(PKG_PREFIX)/app/$(APP_NAME)
all: add mssing APP_NAME to vm*-GOARCH builds
2020-07-31 12:42:09 +02:00
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 15:44:39 +02:00
app-local-windows-goarch:
Makefile: remove redundant `-mod=vendor` option when running Go tools The `-mod=vendor` is automatically set when there is a `vendor` directory starting from Go1.14 - see https://go.dev/doc/go1.14#go-command Since the minimum supported Go version for VictoriaMetrics is Go1.17, then the `-mod=vendor` option is no longer needed.
2022-08-07 19:39:05 +02:00
CGO_ENABLED=0 GOOS=windows GOARCH=$(GOARCH) go build $(RACE) -ldflags "$(GO_BUILDINFO)" -o bin/$(APP_NAME)-windows-$(GOARCH)$(RACE).exe $(PKG_PREFIX)/app/$(APP_NAME)
Makefile: prepare vmutils-windows-*.zip archive on `make release-vmutils` command The archive contains the following executables for Windows: * vmagent * vmalert * vmauth * vmctl Other components - vmbackup, vmrestore, victoria-metrics - aren't supported for Windows yet
2021-03-16 19:49:07 +01:00
all: open-sourcing single-node version
2019-05-22 23:16:55 +02:00
quicktemplate-gen: install-qtc
qtc
install-qtc:
Makefile: consistently use `go install` instead of `go get` for installing various binaries needed during build/test/check of the code `go install` is the preferred way for installing go binaries starting from the minimum supported Go version for VictoriaMetrics - Go1.18 - see https://tip.golang.org/doc/go1.18#go-command
2022-09-08 17:43:02 +02:00
which qtc || go install github.com/valyala/quicktemplate/qtc@latest
Makefile: add `make golangci-lint` rule for running `golangci-lint run`; updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/69
2019-06-20 13:30:55 +02:00
golangci-lint: install-golangci-lint
Makefile: remove trailing space after `golangci-lint run` command It is left after ec2c82e8005546849a84731850f4879f9612667b
2023-01-06 01:58:55 +01:00
golangci-lint run
Makefile: add `make golangci-lint` rule for running `golangci-lint run`; updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/69
2019-06-20 13:30:55 +02:00
install-golangci-lint:
Makefile: update golangci-lint from v1.60.1 to v1.60.3 See https://github.com/golangci/golangci-lint/releases/tag/v1.60.3
2024-09-04 14:39:10 +02:00
which golangci-lint || curl -sSfL https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh | sh -s -- -b $(shell go env GOPATH)/bin v1.60.3
Makefile: add `make docs-sync` command for syncing docs contents
2020-06-02 18:12:07 +02:00
Makefile: add `clean-checkers` rule for dropping checker apps used in `make check-all` The `make clean-checkers` command may be useful when the locally installed checker apps are too old, so they must be updated to the newly requested versions by `make check-all`. In this case the fix is to run make clean-checkers check-all
2024-06-25 20:28:38 +02:00
remove-golangci-lint:
rm -rf `which golangci-lint`
Makefile: check for vulnerabilities in used Go packages with govulncheck when running `make check-all` See https://go.dev/blog/vuln
2022-09-08 17:35:31 +02:00
govulncheck: install-govulncheck
govulncheck ./...
install-govulncheck:
which govulncheck || go install golang.org/x/vuln/cmd/govulncheck@latest
Makefile: add `clean-checkers` rule for dropping checker apps used in `make check-all` The `make clean-checkers` command may be useful when the locally installed checker apps are too old, so they must be updated to the newly requested versions by `make check-all`. In this case the fix is to run make clean-checkers check-all
2024-06-25 20:28:38 +02:00
remove-govulncheck:
rm -rf `which govulncheck`
Add `make check-licenses` rule for the ability to manually check licenses in vendored dependencies This is a follow-up for c687536956c6ad820bb6cbb33e1d1e02dfe7c844
2021-05-10 10:54:35 +02:00
install-wwhrd:
Makefile: consistently use `go install` instead of `go get` for installing various binaries needed during build/test/check of the code `go install` is the preferred way for installing go binaries starting from the minimum supported Go version for VictoriaMetrics - Go1.18 - see https://tip.golang.org/doc/go1.18#go-command
2022-09-08 17:43:02 +02:00
which wwhrd || go install github.com/frapposelli/wwhrd@latest
Add `make check-licenses` rule for the ability to manually check licenses in vendored dependencies This is a follow-up for c687536956c6ad820bb6cbb33e1d1e02dfe7c844
2021-05-10 10:54:35 +02:00
check-licenses: install-wwhrd
wwhrd check -f .wwhrd.yml
Reference in New Issue Copy Permalink