github-mirrors/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2024-11-21 14:44:00 +00:00
Code Issues Projects Releases Packages Wiki Activity
VictoriaMetrics/Makefile

280 lines
7.7 KiB
Makefile
Raw Permalink Normal View History

all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
PKG_PREFIX := github.com/VictoriaMetrics/VictoriaMetrics
Follow up after https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5685 (#5686)
2024-01-25 09:03:46 +00:00
MAKE_CONCURRENCY ?= $(shell getconf _NPROCESSORS_ONLN)
Makefile: allow specifying the needed concurrency for make via MAKE_CONCURRENCY env var
2023-11-20 22:55:19 +00: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 12:46:53 +00:00
DATEINFO_TAG ?= $(shell date -u +'%Y%m%d-%H%M%S')
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
BUILDINFO_TAG ?= $(shell echo $$(git describe --long --all | tr '/' '-')$$( \
make: make openssl output parsing symbol number agnostic (#3429)
2022-12-01 15:09:36 +00:00
git diff-index --quiet HEAD -- || echo '-dirty-'$$(git diff-index -u HEAD | openssl sha1 | cut -d' ' -f2 | cut -c 1-8)))
deployment/docker: use cluster-latest tag for docker images from cluster components Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3505
2022-12-20 18:37:59 +00:00
LATEST_TAG ?= cluster-latest
all: open-sourcing single-node version
2019-05-22 21:16:55 +00: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 12:46:53 +00: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> (cherry picked from commit 654c1cb9d1e76b3952a4ab089687f1c059bae879) Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-08-21 09:25:13 +00:00
TAR_OWNERSHIP ?= --owner=1000 --group=1000
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
Makefile: force running Makefile rules if there is a file matching their names
2020-12-18 10:20:01 +00:00
.PHONY: $(MAKECMDGOALS)
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00: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> (cherry picked from commit fabf0b928eaddfa8842573c4c4ba6b8297db1842)
2024-07-11 10:39:42 +00: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 16:22:41 +00:00
include docs/Makefile
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00: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 09:06:55 +00: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-30 23:27:24 +00:00
include package/release/Makefile
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
all: \
all: open-sourcing cluster version
2019-05-22 21:23:23 +00:00
vminsert \
vmselect \
Makefile: do not build vmagent, vmalert, vmauth, vmbackup and vmrestore binaries in cluster branch, since they are identical to binaries in single-node version There are subtle differences between these binaries in cluster branch from binaries in single-node branch such as missing `-httpAuth.*` command-line flags. These differences introduce confusion to users, so let's stop building these binaries from cluster version.
2020-12-18 16:27:04 +00:00
vmstorage
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
all: small updates after PR #114
2019-07-23 16:54:50 +00:00
all-pure: \
vminsert-pure \
vmselect-pure \
Makefile: do not build vmagent, vmalert, vmauth, vmbackup and vmrestore binaries in cluster branch, since they are identical to binaries in single-node version There are subtle differences between these binaries in cluster branch from binaries in single-node branch such as missing `-httpAuth.*` command-line flags. These differences introduce confusion to users, so let's stop building these binaries from cluster version.
2020-12-18 16:27:04 +00:00
vmstorage-pure
all: small updates after PR #114
2019-07-23 16:54:50 +00:00
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
clean:
rm -rf bin/*
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
vmcluster-linux-amd64: \
vminsert-linux-amd64 \
vmselect-linux-amd64 \
vmstorage-linux-amd64
vmcluster-linux-arm64: \
vminsert-linux-arm64 \
vmselect-linux-arm64 \
vmstorage-linux-arm64
vmcluster-linux-arm: \
vminsert-linux-arm \
vmselect-linux-arm \
vmstorage-linux-arm
vmcluster-linux-ppc64le: \
vminsert-linux-ppc64le \
vmselect-linux-ppc64le \
vmstorage-linux-ppc64le
vmcluster-linux-386: \
vminsert-linux-386 \
vmselect-linux-386 \
vmstorage-linux-386
vmcluster-freebsd-amd64: \
vminsert-freebsd-amd64 \
vmselect-freebsd-amd64 \
vmstorage-freebsd-amd64
vmcluster-openbsd-amd64: \
vminsert-openbsd-amd64 \
vmselect-openbsd-amd64 \
vmstorage-openbsd-amd64
Makefile: add missing vmcluster-windows-amd64 target Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/70
2023-03-25 22:33:41 +00:00
vmcluster-windows-amd64: \
vminsert-windows-amd64 \
vmselect-windows-amd64 \
vmstorage-windows-amd64
make: add darwin builds for cluster (#7195) ### Describe Your Changes Add darwin `amd64` and `arm64` builds for cluster binaries build. ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com>
2024-10-08 08:19:04 +00:00
vmcluster-darwin-amd64: \
vminsert-darwin-amd64 \
vmselect-darwin-amd64 \
vmstorage-darwin-amd64
vmcluster-darwin-arm64: \
vminsert-darwin-arm64 \
vmselect-darwin-arm64 \
vmstorage-darwin-arm64
Makefile: speedup `release`, `publish` and `crossbuild` rules by using parallel make
2023-11-20 20:51:33 +00:00
crossbuild: vmcluster-crossbuild
vmcluster-crossbuild:
$(MAKE_PARALLEL) vmcluster-linux-amd64 \
vmcluster-linux-arm64 \
vmcluster-linux-arm \
vmcluster-linux-ppc64le \
vmcluster-linux-386 \
vmcluster-freebsd-amd64 \
vmcluster-openbsd-amd64
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
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 11:22:37 +00: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 19:05:39 +00:00
publish-vminsert \
Makefile: add missing `vmbackup` and `vmrestore` to `all` and `all-pure` targets
2020-02-16 14:55:28 +00:00
publish-vmselect \
Makefile: do not build vmagent, vmalert, vmauth, vmbackup and vmrestore binaries in cluster branch, since they are identical to binaries in single-node version There are subtle differences between these binaries in cluster branch from binaries in single-node branch such as missing `-httpAuth.*` command-line flags. These differences introduce confusion to users, so let's stop building these binaries from cluster version.
2020-12-18 16:27:04 +00:00
publish-vmstorage
all: open-sourcing cluster version
2019-05-22 21:23:23 +00:00
package: \
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 19:05:39 +00:00
package-vminsert \
Makefile: add missing `vmbackup` and `vmrestore` to `all` and `all-pure` targets
2020-02-16 14:55:28 +00:00
package-vmselect \
Makefile: do not build vmagent, vmalert, vmauth, vmbackup and vmrestore binaries in cluster branch, since they are identical to binaries in single-node version There are subtle differences between these binaries in cluster branch from binaries in single-node branch such as missing `-httpAuth.*` command-line flags. These differences introduce confusion to users, so let's stop building these binaries from cluster version.
2020-12-18 16:27:04 +00:00
package-vmstorage
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
Makefile: add `TAG=v... make publish-release` rule for building and publishing a release for the given TAG
2021-11-08 10:29:10 +00: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 11:10:27 +00:00
rm -rf bin/*
Makefile: speedup `release`, `publish` and `crossbuild` rules by using parallel make
2023-11-20 20:51:33 +00: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 10:29:10 +00:00
Makefile: speedup `release`, `publish` and `crossbuild` rules by using parallel make
2023-11-20 20:51:33 +00:00
release:
$(MAKE_PARALLEL) release-vmcluster
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 19:05:39 +00:00
release-vmcluster: \
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 12:42:48 +00:00
release-vmcluster-linux-amd64 \
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
release-vmcluster-linux-arm64 \
release-vmcluster-freebsd-amd64 \
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 08:36:05 +00:00
release-vmcluster-openbsd-amd64 \
make: add darwin builds for cluster (#7195) ### Describe Your Changes Add darwin `amd64` and `arm64` builds for cluster binaries build. ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com>
2024-10-08 08:19:04 +00:00
release-vmcluster-windows-amd64 \
release-vmcluster-darwin-amd64 \
release-vmcluster-darwin-arm64
Makefile: prepare `arm64` and `amd64` release archives for cluster version on `make release` command
2021-04-05 20:01:45 +00: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 12:42:48 +00:00
release-vmcluster-linux-amd64:
GOOS=linux GOARCH=amd64 $(MAKE) release-vmcluster-goos-goarch
Makefile: prepare `arm64` and `amd64` release archives for cluster version on `make release` command
2021-04-05 20:01:45 +00: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 12:42:48 +00:00
release-vmcluster-linux-arm64:
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
GOOS=linux GOARCH=arm64 $(MAKE) release-vmcluster-goos-goarch
release-vmcluster-freebsd-amd64:
GOOS=freebsd GOARCH=amd64 $(MAKE) release-vmcluster-goos-goarch
release-vmcluster-openbsd-amd64:
GOOS=openbsd GOARCH=amd64 $(MAKE) release-vmcluster-goos-goarch
Makefile: prepare `arm64` and `amd64` release archives for cluster version on `make release` command
2021-04-05 20:01:45 +00: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 08:36:05 +00:00
release-vmcluster-windows-amd64:
GOARCH=amd64 $(MAKE) release-vmcluster-windows-goarch
make: add darwin builds for cluster (#7195) ### Describe Your Changes Add darwin `amd64` and `arm64` builds for cluster binaries build. ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com>
2024-10-08 08:19:04 +00:00
release-vmcluster-darwin-amd64:
GOOS=darwin GOARCH=amd64 $(MAKE) release-vmcluster-goos-goarch
release-vmcluster-darwin-arm64:
GOOS=darwin GOARCH=arm64 $(MAKE) release-vmcluster-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 12:42:48 +00:00
release-vmcluster-goos-goarch: \
vminsert-$(GOOS)-$(GOARCH)-prod \
vmselect-$(GOOS)-$(GOARCH)-prod \
vmstorage-$(GOOS)-$(GOARCH)-prod
Makefile: prepare `arm64` and `amd64` release archives for cluster version on `make release` command
2021-04-05 20:01:45 +00: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> (cherry picked from commit 654c1cb9d1e76b3952a4ab089687f1c059bae879) Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-08-21 09:25:13 +00:00
tar $(TAR_OWNERSHIP) --transform="flags=r;s|-$(GOOS)-$(GOARCH)||" -czf victoria-metrics-$(GOOS)-$(GOARCH)-$(PKG_TAG).tar.gz \
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 12:42:48 +00:00
vminsert-$(GOOS)-$(GOARCH)-prod \
vmselect-$(GOOS)-$(GOARCH)-prod \
vmstorage-$(GOOS)-$(GOARCH)-prod \
&& sha256sum victoria-metrics-$(GOOS)-$(GOARCH)-$(PKG_TAG).tar.gz \
vminsert-$(GOOS)-$(GOARCH)-prod \
vmselect-$(GOOS)-$(GOARCH)-prod \
vmstorage-$(GOOS)-$(GOARCH)-prod \
| sed s/-$(GOOS)-$(GOARCH)-prod/-prod/ > victoria-metrics-$(GOOS)-$(GOARCH)-$(PKG_TAG)_checksums.txt
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
cd bin && rm -rf \
vminsert-$(GOOS)-$(GOARCH)-prod \
vmselect-$(GOOS)-$(GOARCH)-prod \
vmstorage-$(GOOS)-$(GOARCH)-prod
Makefile: add `make release` rule for building release tar.gz file with cluster binaries Fixes https://github.com/VictoriaMetrics/VictoriaMetrics/issues/146
2019-08-15 11:05:17 +00: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 08:36:05 +00:00
release-vmcluster-windows-goarch: \
vminsert-windows-$(GOARCH)-prod \
vmselect-windows-$(GOARCH)-prod \
vmstorage-windows-$(GOARCH)-prod
cd bin && \
zip victoria-metrics-windows-$(GOARCH)-$(PKG_TAG).zip \
vminsert-windows-$(GOARCH)-prod.exe \
vmselect-windows-$(GOARCH)-prod.exe \
vmstorage-windows-$(GOARCH)-prod.exe \
&& sha256sum victoria-metrics-windows-$(GOARCH)-$(PKG_TAG).zip \
vminsert-windows-$(GOARCH)-prod.exe \
vmselect-windows-$(GOARCH)-prod.exe \
vmstorage-windows-$(GOARCH)-prod.exe \
> victoria-metrics-windows-$(GOARCH)-$(PKG_TAG)_checksums.txt
cd bin && rm -rf \
vminsert-windows-$(GOARCH)-prod.exe \
vmselect-windows-$(GOARCH)-prod.exe \
vmstorage-windows-$(GOARCH)-prod.exe
Makefile: add `pprof-cpu` rule for inspecting CPU profiles with `PPROF_FILE=/path/to/cpu.pprof make pprof-cpu`
2019-11-04 10:43:26 +00:00
pprof-cpu:
go tool pprof -trim_path=github.com/VictoriaMetrics/VictoriaMetrics@ $(PPROF_FILE)
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
fmt:
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00: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>
2024-10-30 14:22:06 +00:00
gofmt -l -w -s ./apptest
all: open-sourcing single-node version
2019-05-22 21:16:55 +00: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 17:39:05 +00: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>
2024-10-30 14:22:06 +00:00
go vet ./apptest/...
all: open-sourcing single-node version
2019-05-22 21:16:55 +00: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 18:51:56 +00:00
check-all: fmt vet golangci-lint govulncheck
Makefile: enable golangci-lint in `make check_all`
2019-06-20 11:52:48 +00: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 18:28:38 +00:00
clean-checkers: remove-golangci-lint remove-govulncheck
all: open-sourcing single-node version
2019-05-22 21:16:55 +00: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> (cherry picked from commit 334cd92a6c3cdac1aa2102653ffc5e7d9382bfbc) Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-08-30 08:54:46 +00:00
DISABLE_FSYNC_FOR_TESTING=1 go test ./lib/... ./app/...
Makefile: enable golangci-lint in `make check_all`
2019-06-20 11:52:48 +00: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 10:02:06 +00: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> (cherry picked from commit 334cd92a6c3cdac1aa2102653ffc5e7d9382bfbc) Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-08-30 08:54:46 +00: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 10:02:06 +00:00
all: add Pure Go build (pull request #114) Updates #94
2019-07-23 16:26:39 +00: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> (cherry picked from commit 334cd92a6c3cdac1aa2102653ffc5e7d9382bfbc) Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-08-30 08:54:46 +00:00
DISABLE_FSYNC_FOR_TESTING=1 CGO_ENABLED=0 go test ./lib/... ./app/...
all: small updates after PR #114
2019-07-23 16:54:50 +00: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> (cherry picked from commit 334cd92a6c3cdac1aa2102653ffc5e7d9382bfbc) Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-08-30 08:54:46 +00: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 16:26:39 +00: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 15:22:56 +00: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> (cherry picked from commit 334cd92a6c3cdac1aa2102653ffc5e7d9382bfbc) Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-08-30 08:54:46 +00: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 15:22:56 +00:00
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>
2024-10-30 14:22:06 +00:00
integration-test: all
go test ./apptest/...
all: open-sourcing single-node version
2019-05-22 21:16:55 +00: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 17:39:05 +00:00
go test -bench=. ./lib/...
go test -bench=. ./app/...
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
all: add Pure Go build (pull request #114) Updates #94
2019-07-23 16:26:39 +00: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 17:39:05 +00: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 16:26:39 +00:00
all: open-sourcing single-node version
2019-05-22 21:16:55 +00: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 18:06:30 +00: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 19:01:15 +00:00
go mod tidy -compat=1.23
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00:00
go mod vendor
all: open-sourcing single-node version
2019-05-22 21:16:55 +00:00
all: open-sourcing cluster version
2019-05-22 21:23:23 +00: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 17:39:05 +00:00
CGO_ENABLED=1 go build $(RACE) -ldflags "$(GO_BUILDINFO)" -o bin/$(APP_NAME)$(RACE) $(PKG_PREFIX)/app/$(APP_NAME)
all: small updates after PR #114
2019-07-23 16:54:50 +00: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 17:39:05 +00:00
CGO_ENABLED=0 go build $(RACE) -ldflags "$(GO_BUILDINFO)" -o bin/$(APP_NAME)-pure$(RACE) $(PKG_PREFIX)/app/$(APP_NAME)
all: open-sourcing cluster version
2019-05-22 21:23:23 +00:00
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00: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 17:39:05 +00: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 10:42:09 +00:00
all: follow-up for d99ba3481b192d581bf6a153e40e5f99a7eb5edf
2022-07-13 13:44:39 +00: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 17:39:05 +00: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 18:49:07 +00:00
all: open-sourcing single-node version
2019-05-22 21:16:55 +00: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 15:43:02 +00: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 11:30:55 +00:00
golangci-lint: install-golangci-lint
Makefile: remove trailing space after `golangci-lint run` command It is left after ec2c82e8005546849a84731850f4879f9612667b
2023-01-06 00:58:55 +00: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 11:30:55 +00: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 12:39:10 +00: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 16:12:07 +00: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 18:28:38 +00: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 15:35:31 +00: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 18:28:38 +00: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 08:54:35 +00: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 15:43:02 +00: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 08:54:35 +00:00
check-licenses: install-wwhrd
wwhrd check -f .wwhrd.yml
Reference in a new issue Copy permalink