osmo-ci

Commit Graph

Author	SHA1	Message	Date
Oliver Smith	288fa2d51e	obs: check_builders: at least 10, fail on error The number of builders connected to the OBS server seems to fluctuate a bit (used to be 14, then 17 now 16). Make sure that we have at least 10 builders connected. Fix that the test didn't exit with 1 on error. Related: https://obs.osmocom.org/monitor Change-Id: Iedd506601a5450550e21bf701309b4ea79a3d897	2022-11-04 15:08:00 +00:00
Oliver Smith	f52c26a695	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	2022-10-26 08:35:05 +00:00

Author

SHA1

Message

Date

Oliver Smith

288fa2d51e

obs: check_builders: at least 10, fail on error

The number of builders connected to the OBS server seems to fluctuate a
bit (used to be 14, then 17 now 16). Make sure that we have at least 10
builders connected. Fix that the test didn't exit with 1 on error.

Related: https://obs.osmocom.org/monitor
Change-Id: Iedd506601a5450550e21bf701309b4ea79a3d897

2022-11-04 15:08:00 +00:00

Oliver Smith

f52c26a695

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

2022-10-26 08:35:05 +00:00

2 Commits