aboutsummaryrefslogtreecommitdiffstats
path: root/debian-repo-install-test
AgeCommit message (Collapse)AuthorFilesLines
2021-01-25rename {debian => debian9}-repo-install-testOliver Smith2-11/+0
Prepare to add debian10-repo-install-test. Make it consistent with centos8-repo-install-test. Related: OS#4969 Change-Id: I2ea18997019ebaa013c258996f5131386bcd6426
2021-01-25debian-repo-install-test: remove Release.keyOliver Smith2-25/+1
Make debian-repo-install-test simpler before copying it for debian10. Don't install Release.key, as it is getting downloaded on demand in the related repo-install-test script since osmo-ci I91e7a208d8f5cb50f8baa2fde0eb979aae91da8f. Related: OS#4969 Change-Id: Ia2ba9de264531502e2b0b9f42d7a4ecd34375851
2020-12-01common: Automatize UPSTREAM_DISTRO name based on image namePau Espin Pedrol1-1/+2
Similar to what is already done with DISTRO, which points to given image of ours based on name. This time we do the same with upstream images, such as debian:stretch or centos:centos8. This way, for instance calling docker_images_require "osmo-bsc-latest-centos8" would try to build the osmo-bsc-latest/Dockerfile file starting from a centos8 image. Change-Id: I33cb21aa024396974559fd98f9f3c64e2c351eda
2020-11-02introduce 'REGISTRY' argument to all DockerfilesHarald Welte1-1/+2
This is initialized to docker.io, keeping the default behaviour if not specified. However, it allows us to specify a private registry later on. Related: OS#4839 Change-Id: I32d4ee6256033c809108c1b86cb6b6c58d880f49
2020-05-27debian-repo-install-test: move scripts to osmo-ciOliver Smith3-231/+0
Related: OS#4563 Depends: I777098f19d75f7efbd68b837ccdcd83309429c39 (osmo-ci) Change-Id: If93f37e8d46597a9abc67a4529be9addd65780f5
2020-03-30update OBS Release.key; the old one expired today.Harald Welte1-9/+9
Change-Id: I0dd7d7f54a3eb93ca677f3bdc5e00f62694aaa9e
2019-10-30repo-install-test: disable osmo-ggsn serviceOliver Smith1-1/+1
OsmoGGSN is not able to use the tun4 device from the default config in docker. Since the more strict config checking in [1], it does not just report a warning, but fails to start: <0002> ggsn.c:189 APN(internet): Opening TUN device tun4 <0001> tun.c:184 errno=2/No such file or directory open() failed <0002> ggsn.c:191 APN(internet): Failed to configure tun device Error occurred during reading the below line: no shutdown Failed to open config file: '/etc/osmocom/osmo-ggsn.cfg' Fix the repo install test jenkins job by not checking osmo-ggsn anymore. In theory, we could probably create the tun device on the host, and mount it inside the docker container. But that would require some additional logic to clean it up properly, and it does not seem worth the effort right now. [1] libosmocore Ic9c1b566ec4a459f03e6319cf369691903cf9d00 Change-Id: I15c7a2f38a21cd96c9852ad26f4b4a81798e6593
2019-07-26debian-repo-install-test: systemctl status -n 200Oliver Smith1-1/+1
Show up to 200 log lines instead of the default (10). Related: OS#3369 Change-Id: Ic72dbf1b4c59a259139187b98e74211d57534dc2
2019-07-25debian-repo-install-test: add fixed servicesOliver Smith1-6/+10
Enable test of systemd services for osmo-sgsn, osmo-pcu, osmo-hnbgw and osmo-bts-virtual. Add issue ID to failing osmo-ctrl2cgi and osmo-trap2cgi services. Depends: Id892e1f4ab2daabbe9824b819b5fed985373b97a (osmo-sgsn) Depends: Ie8001611756b661ff1871508c6248b2e990ba1d7 (osmo-bsc) Depends: I354140f014854f1755b649e40a65e5d88b99c0ec (osmo-iuh) Related: OS#3369 Change-Id: I4e182b396e1a2e36a73384233b1a38a70c7cd5d9
2019-07-23debian-repo-install-test: run systemd servicesOliver Smith2-1/+60
Run systemd services of Osmocom programs, to check if any are not starting properly. Use a whitelist to determine which services must start up, because some are currently broken. Modify the docker run command to support changing the CPU scheduling policy/priority in systemd service files (used by osmo-bts). Related: OS#3369 Change-Id: Ie6385f85560fefa7e7c9dca72cb5e2e914d4507a
2019-07-23debian-repo-install-test: kill already runningOliver Smith1-6/+13
The container grows heavily in size as the test runs, so make sure to always kill existing ones (from stopped jobs) before starting a new one. In order to do that, do not use $BUILD_TAG as container name, which changes with every new jenkins run. Related: OS#3369 Change-Id: Ide795092b656c9f0eb92a075d8f662944089019f
2019-07-23debian-repo-install-test: add docker containerOliver Smith5-28/+50
Add own container with systemd, so we can (in a follow-up commit) run the Osmocom systemd services in this test job. Rewrite the "interactive shell" logic to support the new systemd docker container, and enable it with an INTERACTIVE environment variable instead of hardcoding 'interactive="true"' in the script. While at it, move the Repository.key install to the Dockerfile so it works more like the other docker containers we have. Related: OS#3369 Change-Id: I0348f65a2ac184ba6b001e5130dfc8124e657367
2019-02-20debian-repo-test: blacklist soapysdr0.7Oliver Smith1-0/+2
Fix conflict in debian-repo-test-latest by not explicitly installing soapysdr0.7: dpkg: error processing archive /tmp/apt-dpkg-install-aYn9qf/398-soapysdr0.7-module-lms7_19.01.0-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/SoapySDR/modules0.5-2/libLMS7Support.so', which is also in package soapysdr0.5-2-module-lms7:amd64 16.12.0+dfsg-1 I have tested locally, that debian-repo-test passes with this patch with both FEED=latest and FEED=nightly. Related: OS#3809 Change-Id: Ic7c6b95d20345b39af2ba0d09dddd361696723be
2018-10-23repo-install-test: version test for all programsOliver Smith1-7/+6
We did not test all programs before, because they did not have --version implemented. Now they do. Related: OS#3555 Change-Id: I796f1e34d2c026b11dff89511b667fa457856088
2018-09-21debian-repo-install-test: UNKNOWN in --version?Oliver Smith1-13/+36
With this patch, the debian-repo-install-test script checks if the Osmocom programs as installed from the Debian repository have "UNKNOWN" in their --version output. Relates: OS#3555 Change-Id: I46f18dc86d3e257c772a6db8539027aad26e24a8
2018-09-19debian-repo-install-test: new binary package testOliver Smith4-0/+148
Installs most packages from the Osmocom Debian repository into a plain debian:stretch container and call the osmo-* binaries with --version (or -h). The list of packages is automatically generated with aptitude, so the job does not need to be changed for every new package. There's also a new blacklist.txt file with a list of packages, that will not be installed in this test. Currently, this is filled with all packages built from the legacy openbsc.git project (some of them are conflicting with newer repositories) and the soapysdr packages (see OS#3541). The feed ("latest", "nightly") can be specified with the FEED environment variable, it gets read by jenkins.sh (defaults to nightly). Change-Id: I0f0a8b4f0ccd706cd1af98fe25accd6fd410e007 Relates: OS#3176
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-27 10:53:15 +0000