aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorOliver Smith <osmith@sysmocom.de>2021-01-21 10:31:03 +0100
committerOliver Smith <osmith@sysmocom.de>2021-01-21 10:44:59 +0100
commit867b6de1170369dd3d7a33eeb711179bccba7c9c (patch)
tree64df095feb653a14c8c43489dff762fb57697cf9
parent48c966a305daac692e49ce01b6165e9945b5f317 (diff)
jobs/repo-install-test: run a few hours later
Give OBS more time to build the repository, before verifying that we can install all packages from the repository. Apparently, OBS publishes the repository in WIP state, before all packages for a distribution have been built. This leads to problems in the "nightly" and "next" repositories. In contrary to "latest", we do not bump soname versions when doing ABI changes, so we require the user to have all installed Osmocom packages built from the same timestamp. With recent changes in the OBS scripts, we enforce this by having all packages built from the same timestamp depend on the exact version of a dummy package with that timestamp as version. The repo-install-test installs all packages from the binary repository, and so it fails, as it should, if the repository is in an inconsistent state with some packages built today and some packages built yesterday. Related: OS#4733 Change-Id: I8df9b449d6213b5dca6fd9bf5c06b5c96d468f66
-rw-r--r--jobs/repo-install-test.yml2
1 files changed, 1 insertions, 1 deletions
diff --git a/jobs/repo-install-test.yml b/jobs/repo-install-test.yml
index d16b852..2c26490 100644
--- a/jobs/repo-install-test.yml
+++ b/jobs/repo-install-test.yml
@@ -59,7 +59,7 @@
git-config-name: 'Jenkins Builder'
git-config-email: 'jenkins@osmocom.org'
triggers:
- - timed: "H 04 * * *" # run after osmocom-obs.yml
+ - timed: "H 10 * * *" # run after osmocom-obs.yml
publishers:
- email: