aboutsummaryrefslogtreecommitdiffstats
path: root/jobs/repo-install-test.yml
AgeCommit message (Collapse)AuthorFilesLines
2024-02-14jobs/repo-install-test: remove centos8Oliver Smith1-2/+0
Related: https://osmocom.org/news/246 Related: SYS#6759 Change-Id: I311ccfe61b86e467996022107294ad560eee8bdf
2023-09-13jobs: update trigger timersOliver Smith1-1/+1
Ensure we trigger building new OBS packages first, then wait plenty of time until the binary packages are available (and run jobs in the meantime that don't need them), and only after that we run the jobs that need the binary packages. Otherwise TTCN3 jobs may test the packages from the previous day, and some jobs may fail completely due to packages not being completely built yet. For example, yesterday the new Osmocom CNI releases were tagged, which means the :latest packages also need to be rebuilt (-> building all OBS packages takes longer). The osmocom-release-manuals and -tarballs jobs failed, because the new binary packages were not available yet when they ran. Change all timers to the format "H 20 * * *" to have a deterministic hour and semi-random minute based on the job name. Change-Id: Ib68f9a78bae27a63706a8c95715bf6a244b7bf1d
2023-08-03repo-install-test: add debian12Oliver Smith1-0/+2
Related: OS#6057 Change-Id: I51fa3c5212b5e29f4c2804384781693e8de2c097
2023-04-03jobs: add build-discarder to allOliver Smith1-0/+4
Adjust all jobs that don't have a build-discarder yet and add it there. Related: OS#5980 Change-Id: I531ae52ec7337288e3d82151391224f308ab5f9e
2022-12-09jobs/repo-install-test: adjust for qemuOliver Smith1-8/+2
Related: OS#5365 Change-Id: Ie7675811d1a5d6b7cf7e4378c86d747ef6f7a249
2022-08-13update git URLs (git -> https; gitea/gerrit)Harald Welte1-1/+1
Unencrypted git:// protocol offers no integrity or authentication, making it subject to tampering. Use https:// instead. https://github.blog/2021-09-01-improving-git-protocol-security-github/#no-more-unauthenticated-git https://blog.readthedocs.com/github-git-protocol-deprecation/ Change-Id: Ia44e4127ff87a3d4d747225d3258188a0a891f1b
2022-07-06jobs/repo-install-test: update debian versionsOliver Smith1-2/+2
Run against debian 10 and 11, and not against debian 9 anymore. Related: OS#5601 Change-Id: Iaf7c596e0910ca2ce0fafd2819e79d4659b92514
2021-11-22jobs/repo-install-test: centos8: enable latestOliver Smith1-1/+1
Now that we made a new release including the new .spec.in files, from which the rpms are built, we have the rpms in the repository and can enable the repo install test for latest. Change-Id: I5da2b895d636b348e5aa0539a23fe4d99e8644ae
2021-11-22jobs: disable "next" repositoryOliver Smith1-1/+1
Related: OS#5322 Change-Id: I9efd020813540941f9afa2c03b9127c04465ce91
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
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-15 12:40:39 +0000