Update .gitlab-ci.yml file

main
Maxence LANONE 3 years ago
parent 89fcd7c17c
commit ce21d5ec63

@ -1,45 +1,26 @@
# 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: # To contribute improvements to CI/CD templates, please follow the Development guide at:
# https://docs.gitlab.com/ee/development/cicd/templates.html # https://docs.gitlab.com/ee/development/cicd/templates.html
# This specific template is located at: # This specific template is located at:
# https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Getting-Started.gitlab-ci.yml # https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/C++.gitlab-ci.yml
# This is a sample GitLab CI/CD configuration file that should run without any modifications. # use the official gcc image, based on debian
# It demonstrates a basic 3 stage CI/CD pipeline. Instead of real tests or scripts, # can use versions as well, like gcc:5.2
# it uses echo commands to simulate the pipeline execution. # see https://hub.docker.com/_/gcc/
#
# 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
stages: # List of stages for jobs, and their order of execution image: gcc
- build
- test
- deploy
build-job: # This job runs in the build stage, which runs first. build:
stage: build stage: build
# instead of calling g++ directly you can also use some build toolkit like make
# install the necessary build tools when needed
# before_script:
# - apt update && apt -y install make autoconf
script: script:
- echo "Compiling the code..." - g++ helloworld.cpp -o mybinary
- echo "Compile complete." artifacts:
paths:
unit-test-job: # This job runs in the test stage. - mybinary
stage: test # It only starts when the job in the build stage completes successfully. # depending on your build setup it's most likely a good idea to cache outputs to reduce the build time
script: # cache:
- echo "Running unit tests... This will take about 60 seconds." # paths:
- sleep 60 # - "*.o"
- echo "Code coverage is 90%"
lint-test-job: # This job also runs in the test stage.
stage: test # It can run at the same time as unit-test-job (in parallel).
script:
- echo "Linting code... This will take about 10 seconds."
- sleep 10
- echo "No lint issues found."
deploy-job: # This job runs in the deploy stage.
stage: deploy # It only runs when *both* jobs in the test stage complete successfully.
script:
- echo "Deploying application..."
- echo "Application successfully deployed."
Loading…
Cancel
Save