-
Notifications
You must be signed in to change notification settings - Fork 1
/
Makefile
256 lines (229 loc) · 6.46 KB
/
Makefile
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
# SPDX-License-Identifier: Apache-2.0
# capture the current date we build the application from
BUILD_DATE = $(shell date +%Y-%m-%dT%H:%M:%SZ)
# check if a git commit sha is already set
ifndef GITHUB_SHA
# capture the current git commit sha we build the application from
GITHUB_SHA = $(shell git rev-parse HEAD)
endif
# check if a git tag is already set
ifndef GITHUB_TAG
# capture the current git tag we build the application from
GITHUB_TAG = $(shell git describe --tag --abbrev=0)
endif
# check if a go version is already set
ifndef GOLANG_VERSION
# capture the current go version we build the application from
GOLANG_VERSION = $(shell go version | awk '{ print $$3 }')
endif
# create a list of linker flags for building the golang application
LD_FLAGS = -X github.com/go-vela/vela-email/version.Commit=${GITHUB_SHA} -X github.com/go-vela/vela-email/version.Date=${BUILD_DATE} -X github.com/go-vela/vela-email/version.Go=${GOLANG_VERSION} -X github.com/go-vela/vela-email/version.Tag=${GITHUB_TAG}
# The `clean` target is intended to clean the workspace
# and prepare the local changes for submission.
#
# Usage: `make clean`
.PHONY: clean
clean: tidy vet fmt fix
# The `run` target is intended to build and
# execute the Docker image for the plugin.
#
# Usage: `make run`
.PHONY: run
run: build docker-build docker-run
# The `tidy` target is intended to clean up
# the Go module files (go.mod & go.sum).
#
# Usage: `make tidy`
.PHONY: tidy
tidy:
@echo
@echo "### Tidying Go module"
@go mod tidy
# The `vet` target is intended to inspect the
# Go source code for potential issues.
#
# Usage: `make vet`
.PHONY: vet
vet:
@echo
@echo "### Vetting Go code"
@go vet ./...
# The `fmt` target is intended to format the
# Go source code to meet the language standards.
#
# Usage: `make fmt`
.PHONY: fmt
fmt:
@echo
@echo "### Formatting Go Code"
@go fmt ./...
# The `fix` target is intended to rewrite the
# Go source code using old APIs.
#
# Usage: `make fix`
.PHONY: fix
fix:
@echo
@echo "### Fixing Go Code"
@go fix ./...
# The `test` target is intended to run
# the tests for the Go source code.
#
# Usage: `make test`
.PHONY: test
test:
@echo
@echo "### Testing Go Code"
@go test -race ./...
# The `test-cover` target is intended to run
# the tests for the Go source code and then
# open the test coverage report.
#
# Usage: `make test-cover`
.PHONY: test-cover
test-cover:
@echo
@echo "### Creating test coverage report"
@go test -race -covermode=atomic -coverprofile=coverage.out ./...
@echo
@echo "### Opening test coverage report"
@go tool cover -html=coverage.out
# The `build` target is intended to compile
# the Go source code into a binary.
#
# Usage: `make build`
.PHONY: build
build:
@echo
@echo "### Building release/vela-email binary"
GOOS=linux CGO_ENABLED=0 \
go build -a \
-ldflags '${LD_FLAGS}' \
-o release/vela-email \
github.com/go-vela/vela-email/cmd/vela-email
# The `build-static` target is intended to compile
# the Go source code into a statically linked binary.
#
# Usage: `make build-static`
.PHONY: build-static
build-static:
@echo
@echo "### Building static release/vela-email binary"
GOOS=linux CGO_ENABLED=0 \
go build -a \
-ldflags '-s -w -extldflags "-static" ${LD_FLAGS}' \
-o release/vela-email \
github.com/go-vela/vela-email/cmd/vela-email
# The `build-static-ci` target is intended to compile
# the Go source code into a statically linked binary
# when used within a CI environment.
#
# Usage: `make build-static-ci`
.PHONY: build-static-ci
build-static-ci:
@echo
@echo "### Building CI static release/vela-email binary"
@go build -a \
-ldflags '-s -w -extldflags "-static" ${LD_FLAGS}' \
-o release/vela-email \
github.com/go-vela/vela-email/cmd/vela-email
# The `check` target is intended to output all
# dependencies from the Go module that need updates.
#
# Usage: `make check`
.PHONY: check
check: check-install
@echo
@echo "### Checking dependencies for updates"
@go list -u -m -json all | go-mod-outdated -update
# The `check-direct` target is intended to output direct
# dependencies from the Go module that need updates.
#
# Usage: `make check-direct`
.PHONY: check-direct
check-direct: check-install
@echo
@echo "### Checking direct dependencies for updates"
@go list -u -m -json all | go-mod-outdated -direct
# The `check-full` target is intended to output
# all dependencies from the Go module.
#
# Usage: `make check-full`
.PHONY: check-full
check-full: check-install
@echo
@echo "### Checking all dependencies for updates"
@go list -u -m -json all | go-mod-outdated
# The `check-install` target is intended to download
# the tool used to check dependencies from the Go module.
#
# Usage: `make check-install`
.PHONY: check-install
check-install:
@echo
@echo "### Installing psampaz/go-mod-outdated"
@go get -u github.com/psampaz/go-mod-outdated
# The `bump-deps` target is intended to upgrade
# non-test dependencies for the Go module.
#
# Usage: `make bump-deps`
.PHONY: bump-deps
bump-deps: check
@echo
@echo "### Upgrading dependencies"
@go get -u ./...
# The `bump-deps-full` target is intended to upgrade
# all dependencies for the Go module.
#
# Usage: `make bump-deps-full`
.PHONY: bump-deps-full
bump-deps-full: check
@echo
@echo "### Upgrading all dependencies"
@go get -t -u ./...
# The `docker-build` target is intended to build
# the Docker image for the plugin.
#
# Usage: `make docker-build`
.PHONY: docker-build
docker-build:
@echo
@echo "### Building vela-email:local image"
@docker build --no-cache -t vela-email:local .
# The `docker-test` target is intended to execute
# the Docker image for the plugin with test variables.
#
# Usage: `make docker-test`
.PHONY: docker-test
docker-test:
@echo
@echo "### Testing vela-email:local image"
@docker run --rm \
-e PARAMETER_TO="" \
-e PARAMETER_FROM="" \
-e PARAMETER_HOST="" \
-e PARAMETER_PORT="" \
-e PARAMETER_USERNAME="" \
-e PARAMETER_PASSWORD="" \
-e PARAMETER_AUTH="loginauth" \
-e PARAMETER_SKIPVERIFY="true" \
-e PARAMETER_SENDTYPE="starttls" \
vela-email:local
# The `docker-run` target is intended to execute
# the Docker image for the plugin.
#
# Usage: `make docker-run`
# .PHONY: docker-run
docker-run:
@echo
@echo "### Executing vela-email:local image"
@docker run --rm \
-e PARAMETER_TO \
-e PARAMETER_FROM \
-e PARAMETER_HOST \
-e PARAMETER_PORT \
-e PARAMETER_USERNAME \
-e PARAMETER_PASSWORD \
-e PARAMETER_AUTH \
-e PARAMETER_SENDTYPE \
vela-email:local