-
Notifications
You must be signed in to change notification settings - Fork 0
/
.gitlab-ci.yml
100 lines (92 loc) · 2.69 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
91
92
93
94
95
96
97
98
99
100
# This file is a template, and might need editing before it works on your project.
# This is a sample GitLab CI/CD configuration file that should run without any modifications.
# It demonstrates a basic 3 stage CI/CD pipeline. Instead of real tests or scripts,
# it uses echo commands to simulate the pipeline execution.
#
# A pipeline is composed of independent jobs that run scripts, grouped into stages.
# Stages run in sequential order, but jobs within stages run in parallel.
#
# For more information, see: https://docs.gitlab.com/ee/ci/yaml/index.html#stages
#
# You can copy and paste this template into a new `.gitlab-ci.yml` file.
# You should not add this template to an existing `.gitlab-ci.yml` file by using the `include:` keyword.
#
# To contribute improvements to CI/CD templates, please follow the Development guide at:
# https://docs.gitlab.com/ee/development/cicd/templates.html
# This specific template is located at:
# https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Getting-Started.gitlab-ci.yml
stages: # List of stages for jobs, and their order of execution
- build
- test
# - deploy
cache: &global_cache
key: ${CI_COMMIT_REF_SLUG}
paths:
- .cargo/bin
- .cargo/registry/index
- .cargo/registry/cache
- target/debug/deps
- target/debug/build
policy: pull-push
variables:
CARGO_HOME: ${CI_PROJECT_DIR}/.cargo
api-build-job: # This job runs in the build stage, which runs first.
stage: build
image: openjdk:17-jdk
script:
- echo "Compiling the code..."
- cd api
- ./mvnw compile
- echo "Compile complete."
rules:
- changes:
- api/**/*
api-unit-test-job: # This job runs in the test stage.
stage: test # It only starts when the job in the build stage completes successfully.
image: openjdk:17-jdk
script:
- echo "Running unit tests... "
- cd api
- ./mvnw test
- echo "All tests pass"
rules:
- changes:
- api/**/*
auth-build-job:
stage: build
image: lukemathwalker/cargo-chef:latest-rust-1.68-alpine
script:
- echo "Compiling the code..."
- cd auth
- cargo build
- echo "Compile complete."
cache:
<<: *global_cache
rules:
- changes:
- auth/**/*
users-build-job:
stage: build
image: lukemathwalker/cargo-chef:latest-rust-1.68-alpine
script:
- echo "Compiling the code..."
- cd users
- cargo build
- echo "Compile complete."
cache:
<<: *global_cache
rules:
- changes:
- users/**/*
client-build-job:
stage: build
image: node:18-alpine
script:
- echo "Compiling the code..."
- cd client
- yarn install
- yarn run build
- echo "Compile complete."
rules:
- changes:
- client/**/*