forked from clash-lang/clash-compiler
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy path.gitlab-ci.yml
90 lines (77 loc) · 2.22 KB
/
.gitlab-ci.yml
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
include:
- '/.ci/gitlab/publish.yml'
- '/.ci/gitlab/benchmark.yml'
- '/.ci/gitlab/tests.yml'
stages:
- build
# TODO: add test stage to prevent cache throwouts if test failed?
- publish
# Haddock, doctests, unittests, clash-dev testing. These are single threaded
# tests and therefore suitable for public runners.
tests-8.4.4:
extends: .tests-interruptible
tests-8.8.4:
extends: .tests-interruptible
tests-8.10.2:
extends: .tests-interruptible
tests-8.6.5-singular-hidden:
extends: .tests-interruptible
variables:
MULTIPLE_HIDDEN: "no"
# Testsuite (HDL generation and simulation). Highly parallel and memory
# intensive, should only picked up by beefy (local) runners.
testsuite-8.4.4:
extends: .testsuite-interruptible
testsuite-8.8.4:
extends: .testsuite-interruptible
testsuite-8.10.2:
extends: .testsuite-interruptible
testsuite-8.6.5-singular-hidden:
extends: .testsuite-interruptible
variables:
MULTIPLE_HIDDEN: "no"
# Tests on master. These are marked non-interruptible so we can receive e-mails
# on failed jobs, without receiving false negatives.
ghc-8.4.4-master:
extends: .tests-non-interruptible
ghc-8.8.4-master:
extends: .tests-non-interruptible
ghc-8.10.2-master:
extends: .tests-non-interruptible
ghc-8.6.5-singular-hidden-master:
extends: .tests-non-interruptible
variables:
MULTIPLE_HIDDEN: "no"
# Run benchmarks for isclashfastyet.com
benchmark-8.10.2:
extends: .benchmark
# "Publish" a release candidate
hackage-release-candidate:
extends: .hackage
variables:
HACKAGE_RELEASE: "no"
rules:
- if: $CI_PIPELINE_SOURCE == "schedule"
- if: $CI_PIPELINE_SOURCE == "trigger"
# Release new version of Clash to Hackage
hackage-release:
extends: .hackage
variables:
HACKAGE_RELEASE: "yes"
rules:
- if: '$CI_COMMIT_TAG != null' # tags
# Publish a release candidate (beta/edge) to snapcraft.io/clash
snap-beta-or-edge:
extends: .snap
variables:
RELEASE_CHANNEL: beta_or_edge
rules:
- if: $CI_PIPELINE_SOURCE == "schedule"
- if: $CI_PIPELINE_SOURCE == "trigger"
# Publish a new version to stable channel on snapcraft.io/clash
snap-stable:
extends: .snap
variables:
RELEASE_CHANNEL: stable
rules:
- if: '$CI_COMMIT_TAG != null' # tags