-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy path.gitlab-ci.yml
49 lines (43 loc) · 1.52 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
# This file is a template, and might need editing before it works on your project.
# 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
# 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
image: debian
stages: # List of stages for jobs, and their order of execution
- build
- test
build: # This job runs in the build stage, which runs first.
stage: build
script:
- echo "Getting cmake"
- apt-get update --yes
- apt-get install --yes cmake
- apt-get install --yes git
- apt-get install --yes build-essential
- echo "Compiling the code..."
- mkdir build
- cd build
- cmake ..
- make
- echo "Compile complete."
- mv tests ..
artifacts:
paths:
- tests
cpp:
stage: test
script:
- ./tests --reporter junit --out result.xml
artifacts:
when: always
reports:
junit: result.xml