aboutsummaryrefslogtreecommitdiffstats
path: root/jobs/repo-install-test.yml
AgeCommit message (Collapse)AuthorFilesLines
2021-02-10repo-install-test: add label for relevant nodesOliver Smith1-0/+4
Add the slave axis again, so the jobs aren't stuck forever. I had assumed that without the axis, it would run on any node, but that's not how it works. Add a label for this job, with several nodes attached, like we do it for TTCN-3, master-builds, gerrit-verifications etc. Related: https://jenkins.osmocom.org/jenkins/label/repo-install-test/ Related: OS#4567 Fixes: fcf669 ("repo-install-test: run on all build slaves again") Change-Id: I276ab47f76a0f4db542ca99825ebb019236b4d27
2021-02-08repo-install-test: run on all build slaves againOliver Smith1-5/+0
It was not possible to reproduce the weird rpm errors on admin2-deb9build, which had lead to limiting the build slaves to build2-deb9build-ansible. Enable building on all again. Closes: OS#4567 Change-Id: I82ef1f0c581de8ee826adedd9ecde6b4adaa36ba
2021-01-25repo-install-test: add 'debian10'Oliver Smith1-2/+4
Related: OS#4969 Depends: docker-playground I7addb30aa3f8564dcbdc3f6cf2e2e0cfdf4dd02d Change-Id: If0fc12464b571dc42b33f2a077c77ea6e5120b8d
2021-01-25repo-install-test: rename 'debian' to 'debian9'Oliver Smith1-1/+1
Related: OS#4969 Depends: docker-playground I2ea18997019ebaa013c258996f5131386bcd6426 Change-Id: Iaa2202cca4072b4dc0309e011aba6cb33ed5b8aa
2021-01-21jobs/repo-install-test: run a few hours laterOliver Smith1-1/+1
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
2020-12-07jobs: repo-install-test: Use centos8 as distro namePau Espin Pedrol1-1/+1
We use centos8 instead of centos in all docker-playground.git setups and the infrastructure there expects that kind of naming. Related: OS#4888 Change-Id: Idfbb2c4fc1ca10741406c8ab8930dabe8ce632ee
2020-05-28repo-install-test: update jenkins jobOliver Smith1-0/+69
Rename osmocom-debian-install.yml to repo-install-test.yml to get debian out of the name. Extend it with a new distro parameter and update the description. Adjust the shell section to run the script from its new location (in osmo-ci.git, not docker-playground.git). Turn it into a matrix job, so we can have two parameters (distro, feed) for each job. Related: OS#4563 Change-Id: I777098f19d75f7efbd68b837ccdcd83309429c39