# Fast feedback: this finishes in seconds, so it is not held behind the
3
3
# suite.
4
4
build:
5
image:localhost/gitbay-ci:1
5
image:localhost/gitbay-ci:2
6
6
steps:
7
7
- go build ./...
8
8
- go vet ./...
@@ -13,7 +13,7 @@ jobs:
13
13
# The 20m is under the runner's own 30m limit, so go times out first and
14
14
# says which test hung instead of the runner killing it blind.
15
15
test:
16
image:localhost/gitbay-ci:1
16
image:localhost/gitbay-ci:2
17
17
steps:
18
18
- missing=""; for t in git git-lfs gpg; do command -v "$t" >/dev/null || missing="$missing $t"; done; test -x /usr/sbin/sshd || missing="$missing sshd"; test -z "$missing" || { echo "runner is missing:$missing"; exit 1; }
19
19
- go test ./... -count=1 -timeout 20m
@@ -33,7 +33,7 @@ jobs:
33
33
# `build trigger krz/gitbay vuln` runs it on demand before a release
34
34
# (#177).
35
35
vuln:
36
image:localhost/gitbay-ci:1
36
image:localhost/gitbay-ci:2
37
37
schedule:"0 3 * * *"
38
38
steps:
39
39
- go run golang.org/x/vuln/cmd/govulncheck@latest ./...
@@ -56,7 +56,7 @@ jobs:
56
56
# linux-x64 bundle carries its own JRE, which is why the host needs no
57
57
# Java.
58
58
sonar:
59
image:localhost/gitbay-ci:1
59
image:localhost/gitbay-ci:2
60
60
schedule:"30 3 * * *"
61
61
steps:
62
62
- |
.gitbay/wiki/Admin.org+2−2
@@ -458,7 +458,7 @@ where every repository is trusted. There is no automatic fallback: a
458
458
runner started with =-isolation podman= that cannot find a working
459
459
podman exits rather than running a build unsandboxed.
460
460
461
gitbay's own jobs name =localhost/gitbay-ci:1=, built from
461
gitbay's own jobs name =localhost/gitbay-ci:2=, built from
462
462
=deploy/Containerfile.ci= on the runner host. A job's image must carry
463
463
what its steps need: the suite drives real git, git-lfs, gpg and sshd and
464
464
asserts they exist before running, so the stock runner default would fail
@@ -467,7 +467,7 @@ it immediately. Build or rebuild it with: