Currently job artifacts in CI/CD pipelines on LRZ GitLab never expire. Starting from Wed 26.1.2022 the default expiration time will be 30 days (GitLab default). Currently existing artifacts in already completed jobs will not be affected by the change. The latest artifacts for all jobs in the latest successful pipelines will be kept. More information: https://gitlab.lrz.de/help/user/admin_area/settings/continuous_integration.html#default-artifacts-expiration

Commit ba3158e8 authored by Benedikt Kleinmeier's avatar Benedikt Kleinmeier
Browse files

All content in ".gitlab-ci.yml".

parent 0536d945
Pipeline #89236 failed with stages
in 29 minutes
...@@ -31,11 +31,6 @@ stages: ...@@ -31,11 +31,6 @@ stages:
- integration_test - integration_test
- deploy - deploy
include: .gitlab/ci/templates/deploy_stage_templates.yml
include: .gitlab/ci/templates/test_stage_templates.yml
# Job Definitions
# PLEASE, OMIT FOLLOWING GITLAB PITFALLS: # PLEASE, OMIT FOLLOWING GITLAB PITFALLS:
# #
# 1. "include: .gitlab/ci/windows_jobs.yml" does not work! # 1. "include: .gitlab/ci/windows_jobs.yml" does not work!
...@@ -44,6 +39,73 @@ include: .gitlab/ci/templates/test_stage_templates.yml ...@@ -44,6 +39,73 @@ include: .gitlab/ci/templates/test_stage_templates.yml
# 2. Variables from "variables" section are not expanded correctly in "url" # 2. Variables from "variables" section are not expanded correctly in "url"
# section of an "environment". # section of an "environment".
# # GitLab CI Job Templates
#
# These templates can be used to execute jobs on different runners.
#
# Use GitLab's "include" keyword to include this file and the "extends" to
# extend a template below.
#
# For more details, see https://docs.gitlab.com/ee/ci/yaml/README.html#using-extends-and-include-together
.template_unit_tests:
stage: unit_test
# Skip OpenCL tests by using "-Dtest=!Test1,!Test2,..." because GitLab
# runners do not support OpenCL.
script:
- mvn clean
- mvn -Dtest=!TestConvolution,!TestBitonicSort,!TestCLLinkedList,!TestCLOptimalStepsModel test
- python3 Tools/ContinuousIntegration/collect_line_and_branch_coverage.py
artifacts:
when: on_success
paths:
- "*/target/site/coverage-reports"
expire_in: 1 week
.template_scenario_files:
stage: integration_test
script:
- mvn clean
- mvn -Dmaven.test.skip=true package
- python3 Tools/ContinuousIntegration/run_vadere_console_with_all_scenario_files.py
artifacts:
when: on_failure
paths:
- "log_dir"
expire_in: 1 week
.template_seed_test:
stage: integration_test
script:
- mvn clean
- mvn -Dmaven.test.skip=true package
- python3 Tools/VadereAnalysisTools/VadereAnalysisTool/setup.py install --user
- python3 Tools/ContinuousIntegration/run_seed_comparison_test.py
artifacts:
when: on_failure
paths:
- "Tools/ContinuousIntegration/run_seed_comparison_test.d/output"
expire_in: 1 week
.template_deploy_branch:
stage: deploy
script:
- mvn clean
- mvn -Dmaven.test.skip=true package
- python3 -m zipfile -c ${VADERE_PACKAGE_NAME} VadereModelTests/ VadereGui/target/vadere.jar VadereSimulator/target/vadere-console.jar
- scp ${VADERE_PACKAGE_NAME} di49mur@webdev-mwn.lrz.de:~/webserver/htdocs/builds/branches/${VADERE_PACKAGE_NAME}
when: manual
# Job Definitions
# Jobs for GNU/Linux runner (which is labelled with tag "linux") # Jobs for GNU/Linux runner (which is labelled with tag "linux")
run_unit_tests_on_linux: run_unit_tests_on_linux:
extends: .template_unit_tests extends: .template_unit_tests
......
# # GitLab CI Job Configuration
#
# Goal: Run all jobs defined here on all available runners (GNU/Linux and
# Windows).
#
# ## Job Description Syntax
#
# <job_name>: # Job name which is displayed in web interface.
# stage: <stage_name> # Run "script" commands in this stage. The
# # stages are exececuted sequentially.
# script:
# - <arbitrary_commands> # Here you can execute arbitratry terminal
# # commands. If any of the commands return a
# # non-zero exit code, the job fails.
#
# Procedure: Use GitLab job templates in ".gitlab/ci/templates/" and use them
# in the job description by using the "extend" keyword.
#
# ## References
#
# - https://docs.gitlab.com/ee/ci/yaml/README.html
# Variable Definitions
variables:
VADERE_DEPLOYMENT_BASE_URL: "http://www.vadere.org/builds"
VADERE_PACKAGE_NAME: "vadere.${CI_COMMIT_REF_NAME}.${CI_ENVIRONMENT_NAME}"
# Stage Definitions
stages:
- deploy
include: .gitlab/ci/templates/deploy_stage_templates.yml
# include: .gitlab/ci/templates/test_stage_templates.yml
# Job Definitions
# WATCH OUT: "include: .gitlab/ci/windows_jobs.yml" does not work!
# Seems a bug in GitLab's "include" statement. Therefore, define all jobs
# directly here.
deploy_branch_on_windows:
extends: .template_deploy_branch
tags:
- windows
environment:
name: windows
url: ${VADERE_DEPLOYMENT_BASE_URL}/branches/vadere-console.${CI_COMMIT_REF_NAME}.${CI_COMMIT_SHA}.${CI_ENVIRONMENT_NAME}.jar"
# # GitLab CI Job Configuration
#
# Goal: Run all jobs defined here on all available runners (GNU/Linux and
# Windows).
#
# ## Job Description Syntax
#
# <job_name>: # Job name which is displayed in web interface.
# stage: <stage_name> # Run "script" commands in this stage. The
# # stages are exececuted sequentially.
# script:
# - <arbitrary_commands> # Here you can execute arbitratry terminal
# # commands. If any of the commands return a
# # non-zero exit code, the job fails.
#
# ## References
#
# - https://docs.gitlab.com/ee/ci/yaml/README.html
stages:
- unit_test
- integration_test
- deploy
include: .gitlab-ci-templates.yml
# Jobs for GNU/Linux runner (which is labelled with tag "linux")
run_unit_tests_on_linux:
extends: .template_unit_tests
tags:
- linux
run_scenario_files_on_linux:
extends: .template_scenario_files
tags:
- linux
run_seed_test_on_linux:
extends: .template_seed_test
tags:
- linux
deploy_on_windows:
extends: .template_deploy
tags:
- linux
# Jobs for Windows runner (which is labelled with tag "windows")
run_unit_tests_on_windows:
extends: .template_unit_tests
tags:
- windows
run_scenario_files_on_windows:
extends: .template_scenario_files
tags:
- windows
run_seed_test_on_windows:
extends: .template_seed_test
tags:
- windows
deploy_on_windows:
extends: .template_deploy
tags:
- windows
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment