summaryrefslogtreecommitdiffstats
path: root/docker
AgeCommit message (Collapse)AuthorFilesLines
2018-08-30OsmocomBB: Add lua5.3 for the scriping interfaceHolger Hans Peter Freyther3-6/+12
Change-Id: Ia3bd58b98d1e248a92ddd171fb16a23ca8e0b29d
2018-01-17Install pip tool into containersMax3-3/+3
The pip(2|3) tool is the officially recommended tool to deal with Python packages [1] with much greater flexibility compared to invoking setup.py directly. As a preparation step for using it to install osmo-python-tests let's add it to container images. [1] https://packaging.python.org/guides/tool-recommendations/ Change-Id: If2702c71cd268ca688e9ecc264f8cd1257c27899
2018-01-15docker: rebuild: if building fails, try a --no-cache buildYour Name1-1/+3
Building a docker image depending on a debian upstream has the problem that an intermediate build result will depend on an APT package archive that is probable to become outdated. It's necessary to do an 'apt-get update' regularly to get the newest package archives and be able to install new packages. We never know which 'apt-get install' steps we might be editing, so we'd have to add an 'apt-get update' before each, or use an ADD line to find out whether the package archive has changed, before each and every apt-get install step. We're likely to miss those in the future, and it would be a large, complex change. Instead, try to build the docker image with --no-cache in case a cached build has failed. This should fetch the most recent debian upstream with a proper archive. Fixes the current problem that the rebuild_osmocom_jenkins_image.sh is stuck on various build slaves, should trigger a --no-cache build on each slave. Change-Id: I37110287dabd53d3537d94ecd74cf513396971b3
2018-01-15docker: debian: install stow IN THE RIGHT dockerfileNeels Hofmeyr1-1/+1
Recent change I8f5012419495a656912b7b71e4f76ce102c6b63a adds use of stow in osmo-build-dep.sh, hence our jenkins build processes now require the 'stow' dependency. Add 'stow' to our debian docker images, used for various builds (those that invoke 'docker' in the jobs/master-builds.yml and jobs/gerrit-verifications.yml to produce concurrent builds). A recent commit made this change in the Dockerfile.deb8_* dockerfiles, in the assumption that the jenkins one would depend on that, which is actually not the case. Instead, add stow in the dockerfile that is actually used in the jenkins jobs. (It is not harmful to still keep the added dependency in the other two dockerfiles.) Change-Id: If97176f4aea66c42a6820f14ceb4b91369841ca0
2018-01-15docker: debian: install stow, now used in various buildsNeels Hofmeyr2-2/+2
Recent change I8f5012419495a656912b7b71e4f76ce102c6b63a adds use of stow in osmo-build-dep.sh, hence our jenkins build processes now require the 'stow' dependency. Add 'stow' to our debian docker images, used for various builds (those that invoke 'docker' in the jobs/master-builds.yml and jobs/gerrit-verifications.yml to produce concurrent builds). Note: the Dockerfile.deb8_i386 doesn't seem to be used, currently. Add stow there anyway. Change-Id: I7a44ba5ed130a3311460185507f76151c6daa7f1
2018-01-12docker osmo jenkins: osmo-py-tests: use contrib/jenkins.sh to installNeels Hofmeyr1-1/+1
No need to duplicate the install steps we have in osmo-python-tests/contrib now. Also runs the tests. Change-Id: Ibb8eb04e3a5c9c5dcc9b99c83425d2604378f960
2018-01-12Install setuptools in docker imagesMax3-0/+9
Make sure that python-setuptools are installed for both python v2 and v3 to make sure osmo-python-tests can be installed. Change-Id: I3ecd96af2e2c0c7d141977639103d71e46c0cdc5 Related: OS#2821
2017-11-29docker for jenkins: update on changes in osmo-python-testsNeels Hofmeyr1-0/+1
Download (ADD) the latest patch from git.osmocom.org so that the image gets rebuilt when new changes were merged to master. Change-Id: I215f5f6504018d589fa44776a332757a7b870d53
2017-11-29jenkins docker: move smalltalk to separate DockerfileNeels Hofmeyr2-16/+16
To reduce docker image rebuild time, move the Smalltalk related commands to a separate file, which is currently not built by rebuild_osmocom_jenkins_image.sh since there are no jenkins builds using that yet. Change-Id: I1142f068100ef07ce7f177adaa8a0fe2fedb1b7b
2017-11-28jenkins docker: drop hardcoded osmo-deps.shNeels Hofmeyr1-13/+0
The jenkins invocation of the docker image commonly includes the osmo-ci scripts via binding ~/bin to an up-to-date checkout. We don't need another version of osmo-deps.sh in /usr/local/bin. Change-Id: I5ce9ab992afa3c5a7a0bb13b55cae016bc8e805f
2017-11-28jenkins docker: also install py3 scripts of osmo-python-testsNeels Hofmeyr1-1/+1
Allow using the osmo_verify_transcript_{ctrl,vty}.py scripts from the docker image. Change-Id: I27d02d516c1cccd5a2447ee8d76ae476d0951d56
2017-08-25jenkins: Copy Dockerfile and script from buildhostHolger Hans Peter Freyther2-0/+71
We are not using the Docker registry due difficult GPL compliance but build the image on the build node itself. After prototyping if containers can be used for building these files remained forked on the node. These days it seems to be easier to complain than to say thank you that this new approach has its merits. Copy the files from the build slave to the directory they should have been in. Change-Id: Icb0406f96b0c18e77be51ad8317c2668fb23a45e
2016-04-24docker: Add files with all build dependenciesHolger Hans Peter Freyther2-0/+70
Create a clean build environment for amd64/i386 based on debian jessie. Once an official build and sadly once someones 32bit build # Build sudo docker build -t osmocom:ci_debian8_32bit -f Dockerfile.deb8_i386 . sudo docker build -t osmocom:ci_debian8_64bit -f Dockerfile.deb8_amd64 . # Run sudo docker run -it --rm=true osmocom:ci_debian8_32bit bash