Age | Commit message (Collapse) | Author | Files | Lines |
|
This Docker image allows building and running Asterisk from git.
Default config is to build the sysmocom fork used to develop new
features (hence pointing to sysmocom/master branch in that repo.
Related: SYS#6782
Change-Id: Iaa3816f8ceefac8956e61e15f79ed708dec55238
|
|
Related: OS#6204
Change-Id: Iefc43ffa47f443f2826b8979d4dd0c5542dda1c5
|
|
Update the Makefile, so it does not pick the wrong base distribution
when running make in e.g. osmo-bsc-master directly (without going
through ttcn3-*/jenkins.sh as jenkins does).
Change-Id: I31b2a1b8c70b973f4ec0f93d6e9e5e417afec994
|
|
- Add a docker container to run osmo_dia2gsup from git master.
- Add infrastructure to run the osmo-dia2gsup container against
osmo-ttcn3-hacks.git/dia2gsup testsuite.
Related: OS#5757
Change-Id: I646096d5a010df02af75aefa33b023b55997a6d7
|
|
Related: OS#5557
Change-Id: I880f8134e4f7e6ae4125237e6b3983c04cea9ec6
|
|
Change-Id: I0ff3e8f298bd0d743b91d41620623d14911fef63
|
|
Change-Id: I6060364843b1a3e3547a45d98a1248ead22f3970
|
|
Add --rm to the "docker run" line in make/Makefile, and remove it from
RUN_ARGS.
Related: https://osmocom.org/projects/osmocom-servers/wiki/Docker_cache_clean_up
Related: SYS#5827
Change-Id: Iea063aa39a08397ea64d2018b433991a130e7f56
|
|
Allocating a pseudo-TTY (-t, --tty) fails when 'run' is executed
inside of a Jenkins or cron script. This change fixes
ttcn3-bts-test, which invokes 'run' to fetch the config files.
Change-Id: If22f682be4f004c5bb43e65098079a4f4fe6158d
Fixes: If15461240f3037c142c176fc7da745a1701ae3f8
|
|
Building of some images may require additional options to be passed.
Change-Id: Id1761062ac6ec1d1a4eb6a6b724e42cf576c848f
|
|
Change-Id: I29f85a18f5629e50dc1db527e931a248ab69f8e4
|
|
Starting with release 1.2.0 of both repos, osmo-hnbgw binary is in
osmo-hnbgw.git, not osmo-iuh.git anymore.
Change-Id: I4ac6ede6a5b25ada211674bf3c46d79d7720a4bc
|
|
So far we were using ancient Debian 9 (stretch) for our IUT
containers. Let's upgrade that to Debian 11 (bullseye).
Related: OS#4969
Change-Id: Ic6bece9cb695e6eccfcb1e83fdbf1048724a3cf9
|
|
Change-Id: I35e5324d981be8130fbc4e6dcd3e8933181e6821
|
|
Change-Id: I676c5525effe8f34ae11f7b8ed4da0d8961209bf
Related: SYS#5602
|
|
Make it possible to set a different mirror for debian-stretch-titan than
for all other containers. 2021q1 doesn't have the eclipse-titan package
and it doesn't make sense to build it there.
I've thought about adding OSMOCOM_REPO_TESTSUITE_PATH and
OSMOCOM_REPO_TESTSUITE_VERSION too, but we don't have any use for these
right now. Let's add them later if we should need them.
Related: SYS#5370.
Change-Id: I7187473c2188a864b60b03789eff62e0a527404a
|
|
Allow to change the path between OSMOCOM_REPO_MIRROR and
OSMOCOM_REPO_VERSION. While at it, tweak related comments (comment above
the variable as usually, replace "repo" wording with "feed" for the
latest/nightly variable as we usually refer to it as feed), and mention
OSMOCOM_REPO_* in README.md.
In order to be able to use a different mirror for testsuite and systems
under test, the testsuite related Dockerfiles (osmocom-bb-host-master,
debian-stretch-titan) are not using OSMOCOM_REPO_PATH. We could add a
OSMOCOM_REPO_TESTSUITE_PATH on demand, as mentioned in the next commit.
Related: SYS#5370
Change-Id: I8010a4d49d4620a5c47c2ff4f909a9aeeaad7b73
|
|
Allow to give the user running inside docker the same UID as the user
outside.
Change-Id: I4b3689a626c50c9ac38eca6b5449b8ec0344c3de
|
|
Maintaining several versions of the same file in different folders
is a bad idea, because at some point their content gets out of sync.
This is exactly what happened to 'respawn.sh': sleep()ing was only
implemented in 'osmo-bts-master/respawn.sh', other versions of this
file would simply ignore '$SLEEP_BEFORE_RESPAWN'.
The easiest solution would be to have all common files in a single
directory, however Docker does not allow to ADD files from outside
of the build context. In other words, all files must be in the
same directory as the Dockerfile itself.
Modify 'make/Makefile' in order to copy the contents of common
directory to the current build context ('pre-build' target) and
remove it after building ('post-build' target).
Change-Id: I3ec86c8610b3b43d39ea8e3da444861d317ced4e
|
|
Change-Id: I87a425515692e62df7b593a3c2a5b88a765d217d
|
|
Uses the new repo split off of osmo-sgsn
Related: OS#4992
Change-Id: I1e7ede4d1da54e3bcb286213b34401bd9dcf7cc1
|
|
See osmo-ran/README.md in this commit for a description.
Related: SYS#4889
Change-Id: If5d22e9fa818310cbb4adc34bd7aceb4416ec969
|
|
This allows easily changing to another osmocom repo base URL if the
default one is down.
Related: OS#4862
Change-Id: I8010b08f3dabacfb3c13a44eece6c7a490e0742e
|
|
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
|
|
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
|
|
gr-gsm-master is using it but it cannot be overriden. Similarly iy can
be helpful to do so in temporarliy modified images when testing
libosmocore features.
Change-Id: Ia9f26f3513da339d2255a0f6b2277682fe15bdf2
|
|
Prepare for distro-specific osmo-* images. While at it, put each
--build-arg on a separate line for readability.
Related: OS#4564
Change-Id: I1bf1c46295035a073e440faea3696ce53e7d7985
|
|
This set up allows running a typical osmo-gsm-tester set up with a main
unit (ogt-master) attached to one (or more) slaves where resources are
located and processes are run.
As an example, current config allows running an iperf3 test over an srsLTE
stack using the ZeroMQ backend.
Change-Id: Iac7c0b613048ce332642d3957c55cc7c53b56d42
|
|
Change-Id: Ia289f8e71e8bb6c59b1caa7a23981a1f08a2f49e
|
|
Change-Id: Ib51a84560bad521d0adf4bb883c10418c51468a2
|
|
Previously we could only set OSMO_TTCN3_BRANCH as environment variable
to build a test other than master.
This patch adds environment variables for all osmo-*-master images which
allow docker tests to be executed for an arbitrary commit.
The origin/ prefix from the git checkout command is removed so the
*_BRANCH variable doesn't have to contain branch names, but van also
contain arbitrary commits. This shouldn't have any adverse effect as we
only have one remote in the checkout.
Change-Id: If3bc5fae07cf63c4fef68306be4c4328660bc869
|
|
Don't abort with the following error, when running 'make' without
setting the PULL environment variable:
../make/Makefile:20: *** Recursive variable 'PULL' references itself (eventually). Stop.
This fixes a regression from Change-Id
I1076bbb7d77bdc99f5d60d641c09ce965fb9dfc6.
Related: OS#3869
Change-Id: I4b4772e9ed6e07ab00943154265c9cbdea22a2f5
|
|
Prevent building docker images on top of outdated Debian images, where
the package download feeds have been disabled. Use 'docker build --pull'
instead of 'docker build', whenever the "FROM" line in the Dockerfile
does not contain '$USER' (meaning this is an upstream image).
Checking the FROM line is necessary, as downloading '$USER' images will
fail (we never upload those).
Related: OS#3869
Change-Id: I1076bbb7d77bdc99f5d60d641c09ce965fb9dfc6
|
|
Set the OSMO_TTCN3_BRANCH build argument from ttcn3-*/Dockerfile from
the environment variable of the same name, so it can be changed when
building the images with 'make' or './jenkins.sh'.
Dockerfiles that do not have a OSMO_TCCN3_BRANCH build arg produce a
warning. But this is also the case with Dockerfiles that don't have an
USER build arg, and avoiding the warning would only be possible with a
much more complex patch.
Change-Id: If2c312ff9206d1613fc19f41bd088c9aad523684
|
|
This got broken in Change-Id If2e3cc7693ce5e7c1c95d2f81e302c72bb4230be
Change-Id: I97f9eb3f203301ebc2315ff38216d5b4502eb3d2
|
|
Change-Id: Idaa55b636031afd214853ccfcf6c9e3b097050b1
|
|
Change-Id: Ie44144f25fd5f801ceeed904f6d19521b333ed0d
|
|
Change-Id: I73b2ed5794c75d09b166bc65ac79b9cbe3764ad4
|
|
Change-Id: If2e3cc7693ce5e7c1c95d2f81e302c72bb4230be
|
|
Te make scripts will generate docker images like
"$username/foobar-test". When depending on an previous image,
the $username must match or the build will about with image not found.
Change-Id: Ied42c3e1de9a2ffaca22ba4cd02e6a398e48e97d
|
|
$(PWD) reflects the dir of 'make' invocation, $(CURDIR) the dir stepped into.
So obtain the current dir from $(CURDIR) instead of $(PWD).
So far, when doing 'make -C osmo-foo-maser', the image's name would be derived
from the root dir's basename and all images were tagged as 'docker-playground'.
With this fix, 'make -C' from anywhere still tags with the proper name.
Change-Id: I1dd0fd1ad89fdee18fdbea851ccc831ad60aeccf
|
|
Tagging each build with a version means we have to clean up lots of
images manually. Let's change this to:
* "make build" aka "make docker-build" only builds as $name:latest
* "make docker-tag" will tag $name:latest as $name:$version
This is racey, but then we don't really need version tags for the images
so far anyway.
|
|
|
|
|
|
upstream git version is 190313ea54af7d175dd3469a39a95654d068b83e
|