Fix osmo-msc crash at start up:
<0009> db.c:621 Failed to create database connection to sqlite3 db 'sms.db'; Is the sqlite3 database driver for libdbi installed on this system?
DB: Failed to init database: sms.db
It would be better if the Debian package pulled in this dependency
automatically, see OS#3771.
Related: OS#3767
Change-Id: Ia816aed8dd3b86f44f4454af89cec6f0b9d55dd1
osmo-sip-connector does not have a -M argument, it was probably
confused with osmo-msc's -M, --mncc-sock-path argument.
osmo-sip-connector printed out the following when started with -M, but
otherwise functioned normally. Because it was started with Docker in
background, the message did not get written to the build log.
osmo-sip-connector: invalid option -- 'M'
Change-Id: Iee983a8aafe8cade67b76927721fc26e5af966d7
Remove hardcoded /usr/local/bin/ paths from jenkins.sh. This caused the
*-latest tests to fail, as they have the Osmocom binaries in /usr/bin
instead of /usr/local/bin.
Related: OS#3767
Change-Id: I9d1427e66028ffd15fed211b2dab5adc37718666
Do not try to run a osmocom-bb-host-latest docker image, which does not
exist as we are not tagging release versions for osmocom-bb (yet).
This was done right in the docker_images_require call at the top
already (which is why it did not try to build such a "-latest" image),
but then the script tried to use the "-latest" images anyway (instead
of hardcoding "-master").
Related: OS#3767
Change-Id: Ib743f09c71d93bf4c4ad947ef62b37de6b2d7ecc
docker_images_require() must fail when a new image can not be built,
even if an old image already exists.
We have this situation in a lot of the -latest tests right now, which
makes it harder to find the actual error.
Note that we can't simply use #!/bin/sh -e in all the jenkins.sh
scripts that source jenkins_common.sh, because they must be able to
clean up the docker containers on failure. So they can't abort
somewhere in the middle of the scripts. We could rewrite them to do the
clean up in a trap, but this should be done in a separate commit.
Related: OS#3767
Change-Id: I7039089457b62b8798a79c5efd62bd91622986d3
Since Ib2335d02ea545aff837aadd49f15b2fdb418c46e, this VTY option
is deprecated in osmo-bsc, so let's actualize the config files.
Change-Id: I709e1afd2a9cccdc92eec312dff607947a10c299
In I7736abd85407c186856be9f1a22613a1fa6e0c32 'mp_bb_trxc_ip' was
renamed to 'mp_bts_trxc_ip'. Let's correct the config.
Depends-On: (TTCN) I7736abd85407c186856be9f1a22613a1fa6e0c32
Change-Id: I886b652ddfb1afbfcf15f99672cca1d63fd714fe
Update the path to libopenid.jar, to fix the following error and make
the container build again. This change is necessary, because we are
patching a file inside "gerrit.war", and the path to that file has been
changed upstream.
Step 4/8 : RUN unzip /var/gerrit/bin/gerrit.war WEB-INF/lib/gerrit-openid-libopenid.jar ...
---> Running in 815585d87fdd
Archive: /var/gerrit/bin/gerrit.war
caution: filename not matched: WEB-INF/lib/gerrit-openid-libopenid.jar
Change-Id: Iaed2429a776ae587043dc2651293bb354fceeb72
Run the bscnat ttcn3 tests in docker. This uses the osmo-nitb-master
image since osmo-bsc_nat is built there as well.
Change-Id: Ibeebb0325d3d1976225666eb28db0741df2e66f0
Obsoleted by docker_images_require(). The top-level Makefile had the
following drawbacks:
* it was not maintained: many targets were missing, and some of the
existing ones did not build anymore
* make targets have the same names as the folders, so if they are not
listed in the Makefile, it will assume that the target has been built
already (prone to making mistakes)
Extend README.md to describe how to run tests, container caching, how
container dependencies are resolved now and the reasoning for doing
it that way instead of using a top-level Makefile.
Related: OS#3268
Change-Id: Id18a9a7a70f85127e6f6c9447d71764018bdb4ff
Allows writing a generic Jenkins Job Builder config by renaming the
container folders to match the job names. This needs changes in the
Jenkins jobs, as done in Ie433925ee81a61c5788b4a6f2bc5b89c2689d251.
Related: OS#3268
Change-Id: Iedf9a8cd9af1da674e018a08a977490520e602de
Create the ttcn3-bsc-test-sccplite folder, with symlinks to
ttcn3-bsc-test/jenkins-sccplite.sh and ttcn3-bsc-test/sccplite. This
allows writing the jenkins job builder config files in a generic way.
Related: OS#3268
Change-Id: I1d1d277475090cd615a0e2d07a42b2032cdefb9c
Default value "master" of the IMAGE_SUFFIX environment variable can be
changed to "latest" to test the latest stable builds instead of the
nightly ones. Use docker_images_require() to make sure that the required
images are existing and up-to-date before running the tests.
Related: OS#3268
Change-Id: Idbb708ab16cb71bab5069127945b63388222369e
This new function can be used on top of each *-test/jenkins.sh to
automatically build the required Docker images before starting a
testsuite.
The top-level Makefile should also be able to build all Docker images
on which a job depends. But in that Makefile the list of dependencies
can not be specified dynamically, as it will be necessary for OS#3268:
ttcn3-mgw-test may depend on osmo-mgw-latest or on osmo-mgw-master.
This will be used by Idbb708ab16cb71bab5069127945b63388222369e.
Related: OS#3268
Change-Id: I0afdf3400282634fca9b31d57eaeedd6b5c28aa1
We did not test all programs before, because they did not have
--version implemented. Now they do.
Related: OS#3555
Change-Id: I796f1e34d2c026b11dff89511b667fa457856088
Follow up to I6a564206dd81743deb1eb27eca7081bc333d7434 where the
"*-latest" Dockerfiles were introduced. msc, sgsn, sip, stp had
references to "nightly" instead of "latest" in their Dockerfiles.
Related: OS#3268
Change-Id: I1eab031038927043faf6ed8ed30bdf4d4d1624d5
this is just for playing around with it. It might be a good alternative
mailing list archive + access technology in parallel to pipermail (or
soon hyperkitty).
Change-Id: I5882d7637fe8d0ea15040d75709e95b170789c09
For some reason, redmine:3.4 ships with ancient (2014) ruby-openid,
which is no longer compatible with the way how ruby handles HMAC.
Change-Id: I60f6f1ede059accf6b29891abcfe3b2529744e8a
This mirrors osmo-ttcn3-hacks change:
"bsc: inter-BSC HO: add TC_ho_out_of_this_bsc, TC_ho_into_this_bsc"
change-id Id22852d4be7f127d827e7a8beeec55db27c07f03
(As well as removal of the 'add' keyword in change-id
I6a83a8d4ba61b87905c6fae457d4b4eb6078dce9 after osmo-bsc change
I143f21f6069d1a86096cc8240cf69eb7ea9c8ac8.)
Related: OS#2283
Change-Id: I077c2ad2ede900ec43f55655bd740651d3bbe83d
Let's use the well-known hack of adding the "Release" file
of the repository to ensure docker will invalidate the cache if the
repository has changed since the last build.
Change-Id: I54565a4d52221be7e6ded5a339bbf005b58f5998
Let's use the well-known hack of adding the "Release" file
of the respective debian distribution/version to ensure docker
will invalidate the cache if the repository has changed since
the last build.
Change-Id: If6f75db11ef424e46c4915b761f9eca69258a9c5
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
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
Thanks to Piotr, it was discovered that the image building
process fails during full system upgrade:
RUN pacman -Syu
with the following output:
looking for conflicting packages...
Packages (2) ca-certificates-mozilla-* p11-kit-*
...
:: Proceed with installation? [Y/n]
The command '/bin/sh -c pacman -Syu' returned a non-zero code: 1
Looks like the '--noconfirm' flag was missing.
Change-Id: Icb3ccb9a9531686efcebb3e277421c4c05387b09
Instead of hardcoding laforge's username in all FROM statements in the
Dockerfiles, make use of the USER variable (as passed through by the
"make/Makefile" with "docker build --build-arg USER=..."). Thanks to
fixeria for proposing this fix!
This requires running docker-ce, old versions of docker (such as the
one in the official repositories of the latest Fedora) don't support
variables in the FROM line. But docker-ce can be installed after
adding docker's 3rd party repositories.
Closes: OS#3457
Change-Id: Ic5f11c8a4e247f632cb6aea6d147e94c53e0130f
Changes:
* install ca-certificates, so "git clone" doesn't fail
* checkout specific commits (the most recent ones right now), so we
will get the same code every time we build the container and the
patches won't fail to apply in the future
* rebase patch "disable the use of scheduler priorities and mlockall"
on top of master (I couldn't find the commit it was supposed to be
based on)
* delete obsolete patch that fixed compilation
Change-Id: I7cd647684b983384f419b5cfbea0f8dfc7fee70e
The osmo-sip-connector test is already using 172.18.11.x, let's migrate
sccplite to 172.18.12.x to prevent any conflicts when running both tests
on the same build slave (docker instance).
Change-Id: I96beed1f5e01bdb8e77e20f77a459aa006de10fe
ttcn commit I9128f9ad5c372779c38799269393137ba52576cd moves the
modules parameters from NS_Emulation to SGSN_Tests.
Change-Id: I8d46c37b9c932582fe94e670d9347209bb599192
Privileged USB access is required for direct communication
between the image's UHD driver and a host's USRP device.
Change-Id: I8170d2c31b4e28f6a406c50b10b7626f70f36d28
This change introduces a new sub-project - 'gr-gsm-master'.
It was decided to use Arch Linux as the base image, because it
provides the recent version of both UHD and GNU Radio without
tons of dependencies, such as Xorg.
Note: as there in no libosmocore package in Arch Linux, it will
be built from the latest source code.
Change-Id: I115b59dc9eaec5d132f3f64c4ee321173459e9ed
There is no need to keep an additional Docker image with the same
project, because virt_phy can be compiled as a part of the main
image ('osmocom-bb-host-master'). Moreover, virt_phy is not used
at the moment, so let's remove this.
Change-Id: Ifafb044e8350177e60b479b77c8aad78505eabbc
At the moment, this Docker image does contain not only trxcon,
but also FakeTRX, virt_phy, and other host applications, so
let's name it properly...
Change-Id: Ieba2411230efdedc13afcd62b8b3a2153fbaf0cb
Oliver Smith
Vadim Yanitskiy
Pau Espin
Daniel Willmann
Harald Welte