diff options
| author | Oliver Smith <osmith@sysmocom.de> | 2022-10-25 12:27:53 +0200 |
|---|---|---|
| committer | osmith <osmith@sysmocom.de> | 2022-10-26 08:35:05 +0000 |
| commit | f52c26a695edf456dce65bf24235c3a3382a891f (patch) | |
| tree | f3d6d977e20fc77f8ca90e4981040d8e9acd0651 /jobs/osmocom-obs-check-builders.yml | |
| parent | 6b17805553bf4c7e23fdd025b05d5e6102113c38 (diff) | |
jobs: add osmocom-obs-check-builders
Add a job that checks if the amount of connected builders to the OBS
server matches what we expect. This should prevent what we had today,
that it only was noticed by chance several days after all builders
failed to connect and the packages were outdated since then.
I'm not sure if there is a proper api to do this check, but I don't
expect the string we check for to change often so this should work fine.
Change-Id: I6e7c1f206551722d6bfe1631b9c1da8d34d85ba8
Diffstat (limited to 'jobs/osmocom-obs-check-builders.yml')
| -rw-r--r-- | jobs/osmocom-obs-check-builders.yml | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/jobs/osmocom-obs-check-builders.yml b/jobs/osmocom-obs-check-builders.yml new file mode 100644 index 0000000..f378ec1 --- /dev/null +++ b/jobs/osmocom-obs-check-builders.yml @@ -0,0 +1,28 @@ +--- +- project: + name: Osmocom_OBS_check_builders + jobs: + - Osmocom_OBS_check_builders + +- job-template: + name: 'Osmocom_OBS_check_builders' + project-type: freestyle + defaults: global + description: | + Verify that the expected amount of builders are connected to + obs.osmocom.org. + builders: + - shell: | + scripts/obs/check_builders.sh + scm: + - git: + branches: + - 'origin/master' + url: https://gerrit.osmocom.org/osmo-ci + triggers: + - timed: "@hourly" + node: obs + publishers: + - email: + notify-every-unstable-build: true + recipients: 'jenkins-notifications@lists.osmocom.org' |