Those proprietary libraries are required for testing APER based
protocols such as those spoken on IuCS, IuPS and Iuh.
Change-Id: I07489575d0b71c36b35096ecf1e2aab9577cb43e
Newer LimeSuite (at least 7557e291209fc66a78ffa74dd8314e75841f7c96) is
required to have LimeNet-Micro working properly with osmo-trx.
We update to current newest master since other fixes related to sample
rate are applied after the commit mentioned above.
Related: OS#3861
Change-Id: I62779f3bdbc4a459363a1d660d96d5f02f7763c1
Adjust README.adoc to mention "cmd: |" instead of the workaround and
replace this:
cmd: >
# keep first line with less indent to preserve newlines
docker run ...
With that:
cmd: |
docker run ...
Change-Id: I65a06acb76e5d693aa187f9ac38970b73e7fead6
Enable in osmo-nightly-packages.sh, and add as coment in
osmocom-nightly-packages.sh for now (needs a tagged release first).
Related: OS#3899
Depends: I7edb5093e5b58eb3b0f7af2376476db4026db735 (osmo-gsm-manuals.git)
Change-Id: Ideeae4f7846fa5626fe2c1f5a77e07a3c6e626fe
Otherwise every time the interface is added (ie when it goes back to
default netns), the generate name changes due to DEVPATH containing
current name at the end of the path.
Change-Id: I87c686caa23a3b39e48e0762d4323a59be7cd4b8
Currently ofono doesn't catch network interface renaming (takes the name
at ofono startup time).
If a modem crashes, its net iface is unregistered and registered again,
and it can happen that the new name is not the same as before (for
instance, wwan8->wwan0 if wwan0 is located on another netns).
These udev rules allow creating persistent unique names to prevent modem
crashes resulting on interface name changing.
dhcpcd is known to race against udev when managing dev interfaces,
bringing them up before udev sometimes, and then udev is unable to
rename it. By denying dhcpcd from managing modem ifaces (ww* and r*
according to kernel/our rules), we get rid of this issue.
Related: OS#3881
Change-Id: Ic3ef75285aa84f9aa606562cd2f6166de186c1a6
As of Change-Id Id5044b1835190edc948952d207a5196a18669eb1, osmo-remsim
contains Debian packaging information and hence we can build it as part
of our nightly feeds.
We're not yet enabling 'latest' builds as we need to wait for the next
libosmo-abis release for that (requires the IPA keepalive FSM).
Change-Id: Ic367dc95f46cece4bd769061af860fd82b4bd2e9
Exit with error if one of the docker commands is failing (i.e. don't
exit with 0 when building the jessie image failed, but the stretch
image got built properly).
Change-Id: I6faaf9303b4facb0965131615bc73541dd309c51
Prevent building docker images on top of outdated Debian images, where
the package download feeds have been disabled.
Related: Change-Id I1076bbb7d77bdc99f5d60d641c09ce965fb9dfc6
(docker-playground.git)
Related: OS#3869
Change-Id: Id840094aec51bf51d920aaa017a2f99fcb866f55
Fix docker/Dockerfile_osmocom_jenkins.amd64 by fetching jessie-backports
from debian archive.
The jessie image is still being used by various jenkins jobs generated
by master-builds.yml and gerrit-verifications.yml. We want to keep using
it for some more time, to make sure that build testing ("make check")
passes on debian8/jessie, as some users may very well be using old
distros.
See also:
* https://lists.debian.org/debian-devel-announce/2019/03/msg00006.html
* https://unix.stackexchange.com/q/508724
Related: OS#3894
Change-Id: Iba033e64876b7ed9d329c2a636a0ee5eb3af946e
Build osmo-mgw 1.4.0 (which provides libosmo-legacy-mgcp) and install
it into a different temp dir. Allows properly building osmo-bsc 1.2.x,
as soon as a new release is tagged, which makes it use
LIBOSMOLEGACYMGCP_CFLAGS and therefore pick up the include path
properly [1].
osmo-mgw 1.4.0's "make check" doesn't pass right now, so add a check
parameter to build_repo() and disable them when building
libosmo-legacy-mgcp. The checks will get executed later, when the
depends are installed and we are building various tags of Osmocom repos,
including osmo-mgw 1.4.0.
While at it, slightly refactor build_repo() to put all arguments into
descriptive variable names (as it is getting a bit longer now).
[1]: Change-Id: Ibd7948f12da710f8ca2b8fde8870f134308eb908
Related: OS#3867
Change-Id: I63d16f8e44c14dee46e2ef3fd050a421017c56b0
This requires Change-ID I800ebe0f33cf7c86eea65d2e186c6af12fee6db7 from
osmo-ttcn3-hacks.
Fixes: OS#3179
Change-Id: Idee5a986e4cda8db601982ac3f2662bc20fe3f5f
We had some load issues with many things running at once on jenkins.
This will at least make it easier from having colliding ttcn3 jobs.
I also changed ttcn3-sip-test to run at 7:30 instead of 7:00 where
ttcn3-bts-test runs.
Change-Id: I65f346a3fae2811c8314c26d4a5b3a528b8101f9
Build old releases of Osmocom programs and libraries against
"master of the day" to detect breakage.
Redirect each build's output to its own log file, so it is easy to see
what is currently getting build, and what failed. On error, print the
end of the new failing build logs, along with a note to find the full
logs in the jenkins artifacts.
This initial configuration builds the last three release tags of the
Osmocom repositories against master. The configuration can be changed
easily.
Indicate known failures with "err" instead of "ERR" in the output, do
not cause them to fail the build and do not print the beginning of the
error log (it is still in the artifacts). This way, new errors stand out
and don't get overlooked among the known errors.
Related: OS#3765
Change-Id: I7cb45cc40c9930840a3d4e6a86f39e1400478ed3
Support building the legacy openbsc source with osmo-build.dep.sh. This
will be used by the upcoming osmocom-build-old-tags-against-master.sh
script.
Related: OS#3765
Change-Id: I852e103e80bf295f692cf13c4cb38e80fbc19eca
Prepare for the upcoming osmocom-build-old-tags-against-master.sh
script, which will benefit from querying the last n git tags in advance.
Related: OS#3765
Change-Id: I61be4cffb9275cabc1b253f0b298503ad0d3aea4
Properly sort "git ls-remote" output, which looks like:
352f32c9cffef2e5df99cd2f03368dc56c99ee23 refs/tags/0.4.0
Use / as field separator and field no 3, instead of assuming that the
string gets split automatically after the tab character (which it does
not).
Use -V (version sort) instead of numeric sort.
Change-Id: I334e684ac5109fc289b68af78165862148074ea7
Generate a table of Osmocom CNI repositories and their latest tag,
related commit, and last commit on master.
Related: OS#3840
Change-Id: I91cab0139229e6c1c67e889d33b3d984025bc9da
With mobile, virtphy, osmo-bts-virtual we can run e2e tests without
the need of any hardware. Create a dedicated job for it. This avoids
having to share resources (e.g. lock state/ip allocations) with other
builds.
Change-Id: I19993b287cc948dbdfba9d375f80a7904f96ff4a
The binaries built on the Jenkins to be used by the osmo-gsm-tester
require libgnutls.so.30. This is provided by the libgnutls30 package
which is not available on jessie (Debian 8) and a backport requires
some effort.
Re-use the existing Dockerfile for jessie and stretch (Debian 9) using
an argument. Refactor the shell script to pass the right argument. Add
the debian version into the tag name to make space for buster (Debian
10).
Change-Id: I44c8e49a548cb64defd2eba868ec4bd435de90ba
We have been updating some of these files besides no container being
built or used from them. Let's clean this up by removing them.
Change-Id: I7c5b559975e5f9a50368a5bb5bd961bdb9f85270
The osmo-gsm-tester requires a UTF-8 locale to generate the log
messages. Most of our users will have a UTF-8 and it seems okay
to change the default from C to en_US.UTF-8.
Change-Id: I79082a57fd5c9122dbd66997dd48e3ed3e89acb9
Add one more dependency and its dependency for the osmo-gsm-tester
(a separate patch is coming to update the docs).
Change-Id: Icd6a93a8a91c5443b310fdd2123183a8059d31d1
The repository currently doesn't yet have a contrib/jenkins.sh
script, so all verifications will fail. This is intentional,
as it will force the addition of a related script in the first merged
commit.
Change-Id: I713d345240dec319ee07d99e9381fc1af6a2d86d
Alexander Couzens
Harald Welte
Pau Espin
Oliver Smith
Daniel Willmann