RepoMirrors
/
alertmanager
mirror of https://github.com/prometheus/alertmanager
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
alertmanager/Makefile

97 lines
2.8 KiB
Makefile
Raw Permalink Normal View History

Add Makefile and build script
2015-09-25 12:42:14 +00:00
# Copyright 2015 The Prometheus Authors
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
New release process using docker, circleci and a centralized building tool
2015-12-19 23:45:57 +00:00
GO := GO15VENDOREXPERIMENT=1 go
PROMU := $(GOPATH)/bin/promu
Exclude /ui folder from go tests
2017-04-25 13:01:07 +00:00
pkgs = $(shell $(GO) list ./... | grep -v -E '/vendor/|/ui')
New release process using docker, circleci and a centralized building tool
2015-12-19 23:45:57 +00:00
PREFIX ?= $(shell pwd)
BIN_DIR ?= $(shell pwd)
Improve front-end build process We generate binaries whenever `make build-all` is run. If they already exist, we only regenerate them if they are outdated. When one makes changes to the front-end and runs the single command `make build-all` on the root level Makefile, the front-end is rebuild accordingly. `make build-all` will use Docker to build the front-end. If someone prefers to install all the dev dependencies on their local machine instead, one can add the `NO_DOCKER=true` flag. For folks that only want to make back-end changes `ui/bindata.go` is checked in, so they do not have to build the front-end. They still use the `make build` command as before.
2017-05-12 14:49:32 +00:00
FRONTEND_DIR = $(BIN_DIR)/ui/app
New release process using docker, circleci and a centralized building tool
2015-12-19 23:45:57 +00:00
DOCKER_IMAGE_NAME ?= alertmanager
DOCKER_IMAGE_TAG ?= $(subst /,-,$(shell git rev-parse --abbrev-ref HEAD))
Add Makefile and build script
2015-09-25 12:42:14 +00:00
Statically compile assets into binary
2015-11-11 14:34:36 +00:00
ifdef DEBUG
bindata_flags = -debug
endif
Change Makefile target order
2015-11-11 14:50:19 +00:00
Remove 'assets' from default target There are issues with changing timestamps for unmodified files in go-bindata+git.
2015-11-23 15:16:07 +00:00
all: format build test
Add Makefile and build script
2015-09-25 12:42:14 +00:00
test:
@echo ">> running tests"
@$(GO) test -short $(pkgs)
New release process using docker, circleci and a centralized building tool
2015-12-19 23:45:57 +00:00
style:
@echo ">> checking code style"
@! gofmt -d $(shell find . -path ./vendor -prune -o -name '*.go' -print) | grep '^'
Add Makefile and build script
2015-09-25 12:42:14 +00:00
format:
@echo ">> formatting code"
@$(GO) fmt $(pkgs)
vet:
@echo ">> vetting code"
@$(GO) vet $(pkgs)
Improve front-end build process We generate binaries whenever `make build-all` is run. If they already exist, we only regenerate them if they are outdated. When one makes changes to the front-end and runs the single command `make build-all` on the root level Makefile, the front-end is rebuild accordingly. `make build-all` will use Docker to build the front-end. If someone prefers to install all the dev dependencies on their local machine instead, one can add the `NO_DOCKER=true` flag. For folks that only want to make back-end changes `ui/bindata.go` is checked in, so they do not have to build the front-end. They still use the `make build` command as before.
2017-05-12 14:49:32 +00:00
# Will only build the back-end
New release process using docker, circleci and a centralized building tool
2015-12-19 23:45:57 +00:00
build: promu
Add Makefile and build script
2015-09-25 12:42:14 +00:00
@echo ">> building binaries"
New release process using docker, circleci and a centralized building tool
2015-12-19 23:45:57 +00:00
@$(PROMU) build --prefix $(PREFIX)
Improve front-end build process We generate binaries whenever `make build-all` is run. If they already exist, we only regenerate them if they are outdated. When one makes changes to the front-end and runs the single command `make build-all` on the root level Makefile, the front-end is rebuild accordingly. `make build-all` will use Docker to build the front-end. If someone prefers to install all the dev dependencies on their local machine instead, one can add the `NO_DOCKER=true` flag. For folks that only want to make back-end changes `ui/bindata.go` is checked in, so they do not have to build the front-end. They still use the `make build` command as before.
2017-05-12 14:49:32 +00:00
# Will build both the front-end as well as the back-end
build-all: assets build
New release process using docker, circleci and a centralized building tool
2015-12-19 23:45:57 +00:00
tarball: promu
@echo ">> building release tarball"
@$(PROMU) tarball --prefix $(PREFIX) $(BIN_DIR)
Add Makefile and build script
2015-09-25 12:42:14 +00:00
Add Dockerfile and target, change flag
2015-11-12 14:03:09 +00:00
docker:
New release process using docker, circleci and a centralized building tool
2015-12-19 23:45:57 +00:00
@echo ">> building docker image"
@docker build -t "$(DOCKER_IMAGE_NAME):$(DOCKER_IMAGE_TAG)" .
Add Dockerfile and target, change flag
2015-11-12 14:03:09 +00:00
Improve front-end build process We generate binaries whenever `make build-all` is run. If they already exist, we only regenerate them if they are outdated. When one makes changes to the front-end and runs the single command `make build-all` on the root level Makefile, the front-end is rebuild accordingly. `make build-all` will use Docker to build the front-end. If someone prefers to install all the dev dependencies on their local machine instead, one can add the `NO_DOCKER=true` flag. For folks that only want to make back-end changes `ui/bindata.go` is checked in, so they do not have to build the front-end. They still use the `make build` command as before.
2017-05-12 14:49:32 +00:00
assets: go-bindata ui/bindata.go template/internal/deftmpl/bindata.go
go-bindata:
Improve button visibility in UI
2015-11-16 13:47:03 +00:00
-@$(GO) get -u github.com/jteeuwen/go-bindata/...
Improve front-end build process We generate binaries whenever `make build-all` is run. If they already exist, we only regenerate them if they are outdated. When one makes changes to the front-end and runs the single command `make build-all` on the root level Makefile, the front-end is rebuild accordingly. `make build-all` will use Docker to build the front-end. If someone prefers to install all the dev dependencies on their local machine instead, one can add the `NO_DOCKER=true` flag. For folks that only want to make back-end changes `ui/bindata.go` is checked in, so they do not have to build the front-end. They still use the `make build` command as before.
2017-05-12 14:49:32 +00:00
template/internal/deftmpl/bindata.go: template/default.tmpl
@go-bindata $(bindata_flags) -mode 420 -modtime 1 -pkg deftmpl -o template/internal/deftmpl/bindata.go template/default.tmpl
ui/bindata.go: ui/app/script.js ui/app/index.html ui/lib
test: Ensure bindata.go is always up to date This adds three more steps to the Travis tests. 1. Compile Elm -> script.js 2. Bundle html.index & script.js -> bindata.go 3. Check if bindata.go hasn't changed
2017-04-21 13:52:22 +00:00
# Using "-mode 420" and "-modtime 1" to make assets make target deterministic.
# It sets all file permissions and time stamps to 420 and 1
Serve FontAwesome & Bootstrap ourself Instead of using external CDNs for Bootstrap and FontAwesome, this patch makes Alertmanager serve these libraries itself.
2017-06-07 13:50:44 +00:00
@go-bindata $(bindata_flags) -mode 420 -modtime 1 -pkg ui -o \
ui/bindata.go ui/app/script.js \
ui/app/index.html \
ui/app/favicon.ico \
ui/lib/...
Improve front-end build process We generate binaries whenever `make build-all` is run. If they already exist, we only regenerate them if they are outdated. When one makes changes to the front-end and runs the single command `make build-all` on the root level Makefile, the front-end is rebuild accordingly. `make build-all` will use Docker to build the front-end. If someone prefers to install all the dev dependencies on their local machine instead, one can add the `NO_DOCKER=true` flag. For folks that only want to make back-end changes `ui/bindata.go` is checked in, so they do not have to build the front-end. They still use the `make build` command as before.
2017-05-12 14:49:32 +00:00
ui/app/script.js: $(shell find ui/app/src -iname *.elm)
cd $(FRONTEND_DIR) && $(MAKE) script.js
Add Makefile and build script
2015-09-25 12:42:14 +00:00
New release process using docker, circleci and a centralized building tool
2015-12-19 23:45:57 +00:00
promu:
@GOOS=$(shell uname -s | tr A-Z a-z) \
GOARCH=$(subst x86_64,amd64,$(patsubst i%86,386,$(shell uname -m))) \
$(GO) get -u github.com/prometheus/promu
nflog: use alert set instead of hash for deduplication Building a hash over an entire set of alerts causes problems, because the hash differs, on any change, whereas we only want to send notifications if the alert and it's state have changed. Therefore this introduces a list of alerts that are active and a list of alerts that are resolved. If the currently active alerts of a group are a subset of the ones that have been notified about before then they are deduplicated. The resolved notifications work the same way, with a separate list of resolved notifications that have already been sent.
2017-03-13 12:44:36 +00:00
proto:
scripts/genproto.sh
Change Makefile target order
2015-11-11 14:50:19 +00:00
Improve front-end build process We generate binaries whenever `make build-all` is run. If they already exist, we only regenerate them if they are outdated. When one makes changes to the front-end and runs the single command `make build-all` on the root level Makefile, the front-end is rebuild accordingly. `make build-all` will use Docker to build the front-end. If someone prefers to install all the dev dependencies on their local machine instead, one can add the `NO_DOCKER=true` flag. For folks that only want to make back-end changes `ui/bindata.go` is checked in, so they do not have to build the front-end. They still use the `make build` command as before.
2017-05-12 14:49:32 +00:00
clean:
rm template/internal/deftmpl/bindata.go
rm ui/bindata.go
cd $(FRONTEND_DIR) && $(MAKE) clean
nflog: use alert set instead of hash for deduplication Building a hash over an entire set of alerts causes problems, because the hash differs, on any change, whereas we only want to send notifications if the alert and it's state have changed. Therefore this introduces a list of alerts that are active and a list of alerts that are resolved. If the currently active alerts of a group are a subset of the ones that have been notified about before then they are deduplicated. The resolved notifications work the same way, with a separate list of resolved notifications that have already been sent.
2017-03-13 12:44:36 +00:00
.PHONY: all style format build test vet assets tarball docker promu proto