For some reason almost all projects allow to permit building a
specific non-master branch, only osmo-hlr was missing that parameter.
Untested.
Change-Id: Ia4199aa5cfd1f39d34ed7c6104881c68d00dcffa
We're using the build() function not only to build osmocom projects
requiring a .tarball-version file, but also other projects such as
libusrp. Let's make the related git-buildpackage arguments conditional
to whether or not a .tarball-version file exists at all.
Change-Id: I0683cff036a240b1b819f91fbd230d5f9211074c
We're using the build() function not only to build osmocom projects
requiring a .tarball-version file, but also other projects such as
libusrp. Let's make the related git-buildpackage arguments conditional
to whether or not a .tarball-version file exists at all.
Change-Id: I0312a6671e739b803beb583769e4dfc6f44fa091
If a new package is uploaded to OBS, prior to this change,
only the .dsc file is uploaded, not the actual .tar.xz containing
the source code. Let's fix that.
Change-Id: Id1c9e6d112781004238a516b24dd446af0beb95a
At the "autorecon -fi" stage, Osmocom programs either need the .git
directory peresent, or a .tarball-version file in order to determine
the exact source code version.
Normally, "make dist" exists exactly for this purpose: It runs
git-version-gen and saves the result to .tarball-version, and we then
include this file in the .tar.gz we generate.
However, as the nightly paackaging scripts use git-buildpackage, it
bypasses the "make dist" logic and hence we need to
1) manually generate the .tarball-version file
2) copy it over to the directory specified as --git-export-dir
This way, the .tarball-version is inside the tar.xz generated by gbp,
and autoreconf then has something to use as PACKAGE_VERSION.
This commit fixes "UNKNOWN-dirty" in .pc files of libraries, as well
as in "show version" commands on the vty.
Closes: OS#3449
Change-Id: I76e3713f0b01a6110091ff90e8e53aa79533c374
To select if some utilities including qemu/debootstrap/fakeroot will be installed.
Usefull for small setups e.g. simtester
Change-Id: I72f4460b8550da191e74a44be0ee3eeb3b2d7769
For small nodes (e.g. simtester) the full blown packages are not required nor supported.
In this case only the jenkins user and the ssh keys will be setted up.
Change-Id: I469a8012b124516bfd9c4d4dd3a3fe0e1ff80bb6
If string eval encounters an uncovered parse error, it's useful to know which
file it happened in.
Change-Id: I5fe9a3bbdbfb8a995f24596bf09e70ca5bb3fe8a
This came up in
https://gerrit.osmocom.org/#/c/osmo-bsc/+/9671/6//COMMIT_MSG@36
The errors it finds in the current code base are numerous, and many are
intended LOGP .. LOGPC calls. It doesn't make sense to enforce this, but so far
this can be used manually.
Change-Id: Id79389f090a2fded7ff01dc7e3fe9774e7f22ca0
Kevin would like to upload simtrace firmware to ftp.osmocom.org from master
builds. To facilitate, add '--publish' arg, like in master-osmo-gsm-manuals (to
distinguish and not upload from gerrit verification jobs).
Change-Id: I93435aa6f39e9a072754011ae7696b10315f6092
This is the same as done for the master builds in
I6f025c642d5ae57cdda9d7b34bbaeb82ca119354,
seems I forgot to follow up with this one.
Change-Id: I9204ca2f083c8a6a04c6c0fc7d51752a4f1a4830
So far we call with a $(find . -name "*.[hc]") argument list, which might
become too long at some point. Rather include dir walking in the script itself
and allow passing dir arguments as well.
This is backwards compatible, calling with above file args still works.
Change-Id: I36456383906b6295c798b82aa131dda21f8efc02
This seems to resolve the issue where the jenkins job fails due to
missing ssh credentials.
Other jobs can also use this by setting the node property
Change-Id: I23cf2c98f02278a5deb9c4ae8d13438b76538287
Ticket: OS#3338
We currently use range around 10.42.42.1-10 for local dynamically
assigned IP addresses (osmo-msc, osmo-bsc, etc.).
The range 10.42.42.50-60 for local statically assigned IP addresses
(to run osmo-bts-trx sysmocell-5k for instance, where the other end
is cofigured with a static dst addr).
For remote addresses, we use IPs in the range 10.42.42.110-120.
Let's create a new range in 10.42.42.120-130 for remote addressess
assigned by udhcpd server.
nanobts assigned assdresses are moved to the latest group to
differentiate them easily and show that they are not IP addr used
locally.
Change-Id: I9eadb0329a670ce6c2254520d9c86bfbdc898b3a
osmo-trx-lms requires limesuite newer than 17.02, as there were a lot of
features and bug fixes which osmo-trx relies on. Furthermore,
osmo-trx-lms cannot build with that version since it doesn't provide
yet a pkgconfig file.
We cannot use latest tagged release (18.06) since that version has some
build related bugs which have been fixed later on
(c1496679cadff2913cacdaa84afe93bbee76d8e4), hence why we are using
latest available master instead.
Change-Id: If47a3767c7fefbb75923cbfc8eeb921e29393285
Let's move limesuite first since it doesn't depend itself on any osmocom
related package, and osmo-trx depends on it.
Change-Id: I0cdc85a2d0212432bf0c2586230660d363212dcc
Writing '{ 0, NULL }' is actually identical to just '{}', and that's what I use
these days in all sorts of other contexts. So allow this notation as well in
the C code grepper.
Change-Id: I0822d2d997dccbfb31316953a7b6024c317d92cf
In the production setup, there are only 3 valid modems.
Moving the variable into the host_vars so they can have
different amount of modem between rnd & prod.
Change-Id: Ic51a14a339bb9be50504a27a724f6f428ee7304f
uhubctl -p 123456 -a 1 is rejecting because uhubctl detects two hubs.
Selecting only one hub.
Fixes the error message:
Error: changing port state for multiple hubs at once is not supported.
Use -l to limit operation to one hub!
Change-Id: I2e3c248e4eaef39f18ff38d1055db6d552fc4d20
this role can be used to provision developer workstations, which
includes a git clone of all osmocom git repositories as well as
development tools like valgrind, gdb, ccache, wireshark, ...
Change-Id: I1a943079470db97f41c9c38318feb0716daa7cd5
Harald Welte
Pau Espin
Alexander Couzens
Daniel Willmann