summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
6 daysansible: add new deb9build slave on gtplab0HEADmasterHarald Welte1-0/+1
Change-Id: Ide72397cff15c2caa785a117ff095d6f08cb411b
6 daysansible: Fix OBS directory namingHarald Welte6-4/+12
It's really annoying that OBS uses Debian_8.0 and Debian_9.0 (for 8.x and 9.x) and then Debian_10 for 10.x. Let's work around this by some conditional vars_file trickery, hopefully once and for all. Change-Id: I45c4752774f44332b3f9aaf875f49043c03ec5ca
6 daysosmocom-jenkins-slave: Re-orderHarald Welte1-4/+4
Install TTCN3 before installing build-deps, as build-deps requires libulfius, which is only provided by network:osmocom:latest feed, which in turn is only activated as part of the TTCN3 / TITAN installation. Change-Id: I66f1d5f7479a6d028abdac0cc6f4000faa78b135
2020-11-18ansible: add role for 'podman'Harald Welte2-0/+40
podman has one particularly interesting feature which docker rejected years ago: The ability to run a container in a pre-existing namespace. This is quite useful for some of our test setups, particularly those that involve hdlc net-devices Change-Id: I4b14599f39c07ec83fa4222f9d040d443caae3e6
2020-11-17ansible: ogt: Install new dependency python3-watchdogPau Espin Pedrol1-0/+1
As of osmo-gsm-tester.git Change-Id I938602ee890712fda82fd3f812d8edb1bcd05e08, python3-watchdog is required. Change-Id: I35026e82b255cd4e06b4211c4829cd12be59976e
2020-11-15remove all debian8 slavesHarald Welte3-9/+0
we cannot even create new slaves as lxc-create doesn't support debian jessie anymore. Let's focus on Debian 9 + Debian 10 Change-Id: I2fddd460f7d1db755cc9b732b2be80494d26e091
2020-11-15ansible/docker: Use docker.io on architectures not supported by docker-ceHarald Welte1-1/+7
The docker company official builds are only present for amd64, but not for other architectures. Let's use the Debian docker.io package in such situations. Change-Id: Id85137fc0eb7fa5e2b31aa928c78bfdaadc281ac
2020-11-14jobs: master + gerrit: Mark them as running on debian9. not debian8Harald Welte2-2/+2
We actually do the verification inside a (debian 9) docker container anyway, so there's no need to run those on the old debian8 slaves. Change-Id: I2168bd2f0e6221518ece111e29dc604c33eaca6a
2020-11-14ansible: ttcn3-slave: Use libfftranscode 0.3Harald Welte1-2/+2
0.3 is the first version for which we have i386 builds Change-Id: I8bc20e43a82ff797a4f70db476cddaab39fdc2a2
2020-11-14ansible: ttcn3-slave: Fix for Debian 10 slavesHarald Welte1-2/+2
Change-Id: I943e4a8e49e4f95abf1e44dc297d30c950580680
2020-11-14ansible: roles/docker: Add ca-certificatesHarald Welte1-0/+1
If that package is not installed, adding the GPG key fails with SSL certificate verification, at least on a debian10 i386 lxc: TASK [add docker gpg key to apt keyring] ************************************************************* fatal: [gtp0-deb10build32-ansible]: FAILED! => {"changed": false, "msg": "Failed to download key at https://download.docker.com/linux/debian/gpg: Request failed: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1056)>"} Change-Id: I58259a99258c9c7471e1fcf03a3a7b62fa9c6a48
2020-11-06jobs/master-builds.yml: enable manuals for all osmo-bts variantsVadim Yanitskiy1-2/+2
Since Idba84164b90e3d183a20b5eb69cbfe15745e447c, we started to generate separate PDFs for different osmo-bts-variants, so let's enable them all. Otherwise only osmo-bts-{virtual,sysmo} PDFs are generated and uploaded to the server. Change-Id: I517be2d475f57026dab7f001d2298cf1a1aa2c7c Related: SYS#4937
2020-11-05jjb: Add ttcn3-gbproxy-test to ttcn3-testsuites.ymlDaniel Willmann1-0/+10
Fixes: OS#4850 Change-Id: I05d1855a6daea6a67df01a1f9fa65955cfd72661
2020-11-04Add jenkins job to update docker base images on registry.osmocom.orgHarald Welte1-0/+37
Change-Id: Iec2d2e3a43b074cb60f75cbe852351ffa8e0009e Related: OS#4839
2020-11-02ttcn3-testsuites: Set REGISTRY_HOST="registry.osmocom.org"Harald Welte1-0/+1
This will make the Dockerfiles from docker-playground.git use registry.osmocom.org rather than the public docker.io for base distribution images like debian:stretch or the like. This will avoid any strange timeout/EOF problems while doing docker build --pull in our test jobs. Change-Id: If4275cf3c8a5b70a67d742950a35ae8ead59a52e Closes: OS#4839
2020-11-02README.md: Fixup ansible command line for docker loginHarald Welte1-1/+1
We need to do a docker log in as 'osmocom-build' user, not as 'root' Related: OS#4839 Change-Id: I8ea0338e49d332382c9d08b21ee247244f97d141
2020-11-02README.md: Add instructions on how to make jenkins slaves 'log in' private ↵Harald Welte1-0/+4
docker registry Change-Id: Ibf7e8c6ef2b3efd5a0a193501de90797e2d6f080
2020-11-02ttcn3-slave.yml: don't hard-code amd64 as the dpkg architectureHarald Welte1-2/+6
We have no clue what the host architecture will be... Change-Id: I32c0905c8e077faa02984ea67c452fcdb81440da
2020-10-22jjb: obs: Trigger jobs at sme point during 00H instead of 01HPau Espin Pedrol1-1/+1
There's no real need to wait until 01:00, let's try to get packages built before. Change-Id: I9db7108ecaab418f9b657d30c02622c56dc04798
2020-10-22jjb: ttcn3-testsuites: Spread all test grouped around the dayPau Espin Pedrol1-28/+85
Before this patch, only the debian+master jobs were spread around several hours, while debian+latest and centos+nightly were all triggered at midnight. Let's instead run all flavours of teh same test (debian+nightly/latest, centos) around same time but not concurrently by marking blocking one each other so that they are run one after the other. Then, each group is separated by a given time spreading the load over the night + morning. This also means we no longer start tests at 00:00, which means docker images will use software from the day after, since the nightly repositories are built around 01:00. Related: SYS#5121 Change-Id: Ib1f374974444cdd5d829c4e57153137ecd9149f1
2020-10-21osmocom-nightly-packages: Build osmo-smlcHarald Welte1-0/+2
Change-Id: Ibaa87a23659de82bb9ad9767e7fa01331e40d2e9
2020-10-21jenkins: add osmo-smlc to coverity and ttcn3 jobsNeels Hofmeyr3-0/+4
Change-Id: I690962cd8352e255a2bf0ae16aa8ddda68edf10a
2020-09-23build-old-tags-against-master: Ignore some osmo-bts and openbsc versionsPau Espin Pedrol1-0/+4
Some unit tests in those repositories started failing due to a fix in libosmocore logging system where extra coloring tags were printed when not needed. Unit tests in current master of those repositories are fixed to work with both old and new versions of libosmocore since they got coloring disabled in their output, and new patch releases have been done containing the fix, which means last releases already work with both libosmocore version. However, older releases are expected to fail when built against libosmocore master. Change-Id: I03ca926b903a4dcc9967ab5fe455d715cdb9ed45
2020-09-18jobs: Enable --without-sse build variant for osmo-trxPau Espin Pedrol2-4/+6
Change-Id: I47a2067dc25335557dfa93f291f6ca9cd4959735
2020-08-31ansible: osmocom-jenkins-slave: install SRS packages only on debian >= 9Alexander Couzens1-0/+1
Before debian 9 those packages aren't available. e.g. libczmq-dev or libsoapysdr-dev Change-Id: I019ec01dc7e0a53fa4ce9e8579fbafb3916f559b
2020-08-21jenkins: add master + gerrit for osmo-smlcHarald Welte2-0/+2
Change-Id: Iaeb064ed8e7d08db305f1928dc26d16dc6c889dd
2020-08-14ansible: osmocom-jenkins-slave: osmocom_build_deps: install ↵Alexander Couzens1-0/+24
osmo-python-tests for py2 and py3 The osmo-python-tests will be used to test vty commands. The old python2 package are only required to test old images because the current master is only supporting python3. Installing both doesn't conflict because the python site-packages are different for the two version. Change-Id: Ica279e83b763389ababb526336ebd95d45beee7a
2020-08-14old-tags-against-master: Don't build osmo-gsgsn 1.6.0+1.6.1Harald Welte1-0/+2
both tags will not build due to osmo_sockaddr name collisions. Change-Id: Ifd3c0d30897d4d0286fa129f5c17b495a8f2323b
2020-08-09osmocom-latest-packages: Remove limesuite-debian10Harald Welte1-2/+0
Since LimeSuite v20.07.x has been released, we don't need a debian10 specific package anymore. Change-Id: Ibc1337e2500fc37c47a283141fad58a2fb321f05
2020-08-05Revert "nightly-packages: Hard-code LimeSuite to 20.01.0 as 20.07.0 is broken"Harald Welte3-28/+1
This reverts commit e17a4d66d06ad5acb74a728ca378ad0cc9fffdf0, i.e. we are back to building the latest tag, now that v20.07.1 has been released, which actually builds again. However, the package name in debian/changelog has not been updated to reflect that version change, resulting in v20.07.1 being packaged in a package called v20.07.0. Change-Id: I01b77f03924a0b303103fb737dfee15b9c4b0c9c
2020-08-03ansible/docker: set overlayfs2 and ipv6Alexander Couzens3-0/+17
overlayfs2 should be the default anyway. Enable it on all hosts, since it was enabled on older hosts. Change-Id: I20728d6017204c3978e23376baa89de6e91fed1e
2020-07-30nightly-packages: Hard-code LimeSuite to 20.01.0 as 20.07.0 is brokenHarald Welte3-1/+28
See https://github.com/myriadrf/LimeSuite/issues/313 This also reverts the previous commits that removed the work-around for building LimeSuite on Debian10, as that one is still required for v20.01.0 (and not for v20.07.0). Change-Id: Ib70418f0b8a4c6aafa3098b6fa3e240f89112b59
2020-07-30obs-nightly: Remove limesuite-debian10 package altogetherHarald Welte1-2/+0
20.07 builds unmodified on debian10 Change-Id: I24f95efe55e3c88c07e3f313a11d706d6947b4ab
2020-07-30remove limesuite/build-for-debian10.patchHarald Welte1-13/+0
As of yesterday (upstream commit fdfe3d340506a7de4f41d74296e1f32a906700f2), LimeSuite upstream finally builds without patches on Debian 10 Change-Id: Ibbed53f57ac750f39ea20ac73c28c4773c244a6f
2020-07-01latest-packages: build osmo-e1dHarald Welte1-0/+2
Change-Id: Ib74832bff1ce6856ada126c54f5f66c510034af4
2020-06-30nightly-packages: Add osmo-e1dHarald Welte1-0/+2
Change-Id: I71630d9f99e3fe703fc90ce14f3f0c3a82282a0d
2020-06-25ansible/gsm-tester: Install patchelf 0.11 on PATHPau Espin Pedrol1-8/+8
We used to install patchelf 0.10 in a specific path to only use it for some binaries which had bugs with patchelf 0.9 (and other binaries had bugs with 0.10, so we couldn't use 0.10 for all binaries and hence put it in binary). However, 0.11 is fixing both issues so we can use it in all cases, hence we can put it in PATH (/usr/local/bin). Related: OS#4389 Change-Id: Ica30807ecab7b60daee31fe7824b7c848d20c904
2020-06-09jobs: osmo-gsm-tester: Run mass LU and ttcn3 BTS tests nightlyPau Espin Pedrol1-6/+2
Before they were executed almost in a loop, so let's simply run them once per day. Change-Id: Ie42fc1e686d29740e14aaacd69659fe09e66801a
2020-06-09jobs: osmo-gsm-tester_ttcn3: Fix path to jenkins scriptPau Espin Pedrol1-1/+1
There was a directry refactoring a few weeks ago in osmo-gsm-tester and this path was not updated correctly. Change-Id: I580cd9d4a602b3ed1839fb0990ac3816c5e42cbe
2020-06-03remove openbsc from nightly and latest buildsHarald Welte2-4/+0
The only part that we haven't migrated elsewhere is osmo-bsc_nat, which is also really unmaintained at this point. Let's not confuse people into thinking they should actually use this software anymore. Change-Id: Icee165422a52bfe04be103a5b7ebb5c8909c0321
2020-05-30jobs/ttcn3-testsuites.yml: support centos8Oliver Smith1-19/+58
Related: OS#4564 Change-Id: I195437ffe8a8b6cb54de867d6f809c71e8f47ef1
2020-05-28scripts: source common.sh before cdOliver Smith2-2/+2
common.sh tries to set OSMO_CI_DIR now; however this does not work when common.sh was sourced with ". ./common.sh": realpath: scripts/..: No such file or directory Fixes: 7cb8e2d0 ("OBS: add debian10 specific patch for limesuite") Related: https://jenkins.osmocom.org/jenkins/job/Osmocom-build-tags-against-master/455/console Change-Id: Ib326eb0fa769528398335c9cf06dc9c9576c882e
2020-05-28jobs/osmocom-obs.yml: create Osmocom_OBS_next jobOliver Smith1-0/+1
Change-Id: I50dca459d19dca5894b71169ae70a6c6778b2e52
2020-05-28OBS: add osmocom-next-packages.shOliver Smith3-7/+45
Fill the "next" feed with source packages generated from the "next" branch of each Osmocom project, if it exists, with fallback to the "master" branch. Implement as wrapper around osmocom-nightly-packages.sh, so we don't duplicate code and don't need to add more logic to the jenkins job. Adjust all osmo_obs_prepare_conflict calls. Add a comment line on top of each osmocom-*-packages.sh script stating the feed they can be used with. Related: SYS#4887 Change-Id: I0542b6243bdd29d08381fcc82368dcbd30bf9dce
2020-05-28OBS: support more than one conflicting packageOliver Smith1-6/+22
For the upcoming network:osmocom:next repository, it would be inconsistent to have the debian package conflict mechanism only support latest and nightly, even if the next repository is currently not built for debian. Change-Id: I2c07313fbbdffe5571e447059b08fe74c853cef0
2020-05-28repo-install-test: update jenkins jobOliver Smith2-44/+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
2020-05-28repo-install-test: don't mount /dataOliver Smith2-10/+9
The "run-inside-docker.sh" script is running as root (in order to be able to install packages). Do not mount an outside directory as /data inside the image anymore, where the script would write temporary data. This causes problems on jenkins, as the temporary files are written as root and jenkins is then unable to wipe the workspace. I had used this for debugging when I wrote the script initially, but almost the same can be done now with INTERACTIVE=1 and cat on the temporary files. Related: OS#4563 Change-Id: If7e1d83580c2951e7e50181ba7e755b987675e4b
2020-05-28repo-install-test: support centosOliver Smith4-17/+93
Related: OS#4563 Depends: I50743c304728444ede8e0d40b8abef9d17c44d8d (docker-playground) Change-Id: I399360ee6389591180859b52f0ef08883447b90b
2020-05-28repo-install-test: add KEEP_CACHE env varOliver Smith3-0/+30
Keep downloaded binary packages to make test cycles shorter during development. While at it, also document all environment variables. Change-Id: I4d6ebaf460e47f29e023acb0bd78ef52ca80c7cd
2020-05-28repo-install-test: use sh -exOliver Smith1-4/+6
Make it consistent with run-inside-docker.sh by also using -e and -x. This makes development easier. Change-Id: I733164829bf076fb42df3fde725f3e330f8abecc