osmo-ci - Osmocom Continuous Integration

Age	Commit message (Collapse)	Author	Files	Lines
2020-01-15	docker: move to docker-playground.git	Oliver Smith	1	-2/+1
	Instead of building "osmocom:deb9_amd64" from this repository, build "$USER/debian-stretch-jenkins" from docker-playground.git (same Dockerfile). Adjust all jobs to use the new image name. Add a new "update-osmo-ci-on-slaves-dp" jenkins job, which triggers the existing "update-osmo-ci-on-slaves" job whenever docker-playground.git changes. Replace docker/rebuild_osmocom_jenkins_image.sh with scripts/osmo-ci-docker-rebuild.sh, so we can get rid of the docker dir. I thought about dropping the script completely, and directly writing the two lines into contrib/jenkins.sh. But I kept the extra script for convenience, when testing locally. Related: OS#4345 Depends: docker-playground I125ae8a6bcabbd1f485028c79b0abacda0622c3a Change-Id: I30a61aebcadef5536e74edd35e1c75ef77a2da9f
2017-11-28	contrib/jenkins.sh: rather git checkout -f instead of pull	Neels Hofmeyr	1	-1/+1
	Change-Id: Idc672879dcb3d38978e27b90c173f0aa950c4eb1
2017-11-28	contrib/jenkins.sh: update from current jenkins job update-osmo-ci-on-slaves	Neels Hofmeyr	1	-4/+8
	We're not calling this script on the update-osmo-ci-on-slaves job yet. To move over to calling this script, apply some edits we made on the jenkins UI in the meantime. Change-Id: I54d3f56a89934c1c7b0e445b5c447c91bf94d579
2017-11-10	jenkins: Follow the convention and create a jenkins.sh as well	Holger Hans Peter Freyther	1	-0/+12
	Instead of modifying the job on Jenkins, let's do it like in our other projects. Create the diretcory if it doesn't exist and use git pull origin for the Debian9 system. Change-Id: I0ecdc02e3271fe09980f370167277370c599fcfa