Skip to content
Snippets Groups Projects
Commit 42233a61 authored by Walter Lozano's avatar Walter Lozano
Browse files

Add new check-pipelines functionality


To have a single place where to check if infrastructure pipelines are green
add a new functionality based on the gitlab-check script.

Signed-off-by: default avatarWalter Lozano <walter.lozano@collabora.com>
parent 6fb38674
No related branches found
No related tags found
1 merge request!202Add new check-pipelines functionality
Pipeline #769206 failed
......@@ -6,11 +6,13 @@ variables:
Use this to select one of the supported pipelines.
Set to 'folding' to fold updates into a stable release.
Set to 'branching' to branch a new release.
Set to 'checking' to perform check on different pipelines
value: testing
options:
- testing
- folding
- branching
- checking
NOACT:
description: |
Use this to variable to avoid performing changes (dry mode)
......@@ -94,4 +96,29 @@ explain-done:
# do not run on a branch if there's a MR open, run only in MR context
- if: $CI_COMMIT_BRANCH && $CI_OPEN_MERGE_REQUESTS
when: never
- when: manual
\ No newline at end of file
- if: '$PURPOSE == "checking"'
when: never
- when: manual
check-infra-pipelines:
stage: check-infra-pipelines
tags:
- lightweight
needs:
- explain
before_script:
- export DEBIAN_FRONTEND=noninteractive
- apt-get update
- apt-get install --no-install-recommends -y python3-yaml python3-gitlab ca-certificates
script:
- cd check-pipelines
- test "$PURPOSE" != "checking" && ARGS= || ARGS=-e
- ./gitlab-check.py $ARGS -u "$CI_SERVER_URL" -t "$GITLAB_TOKEN" -v 2 -c infra-config.yaml check-pipelines
rules:
# do not run on a branch if there's a MR open, run only in MR context
- if: $CI_COMMIT_BRANCH && $CI_OPEN_MERGE_REQUESTS
when: never
- if: '$PURPOSE == "folding" || $PURPOSE == "branching"'
when: never
- if: '$PURPOSE == "checking" || $PURPOSE == "testing"'
when: on_success
\ No newline at end of file
......@@ -317,9 +317,9 @@ publish-lava-images:
EOF
check-pipelines:
check-branched-pipelines:
extends: .custom_globals_default
stage: check-pipelines
stage: check-branched-pipelines
allow_failure: true
before_script:
- export DEBIAN_FRONTEND=noninteractive
......
......@@ -29,7 +29,8 @@ stages:
- obs-finish-server
- obs-complete
- misc-updates
- check-pipelines
- check-branched-pipelines
- check-infra-pipelines
default:
image: debian:bookworm-slim
......
projects:
- infrastructure/*
status: failed
ref:
- apertis/v2023
- apertis/v2024
- apertis/v2025pre
- main
- master
\ No newline at end of file
......@@ -3,7 +3,6 @@ gitlab_image_project: 'infrastructure/apertis-image-recipes'
image_url: https://images.apertis.org/daily/
releases:
- v2025pre
- v2025dev3
- v2024
- v2023
deployments:
......@@ -18,4 +17,4 @@ string_remove:
string_space:
- '/'
- '">'
scheduled_string: 'Scheduled job: https://lava.collabora.dev/scheduler/job/'
\ No newline at end of file
scheduled_string: 'Scheduled job: https://lava.collabora.dev/scheduler/job/'
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment