osmo-ci - Osmocom Continuous Integration

Age	Commit message (Collapse)	Author	Files	Lines
2018-04-09	osmo-clean-workspace.sh: make more robust against broken git clones	Neels Hofmeyr	1	-4/+25
	Change-Id: Ifa70fd75468b3e21b5c9327ea28bc7a4c8cb549d
2018-04-09	osmo-clean-workspace.sh: cosmetic: no need to clean -e deps	Neels Hofmeyr	1	-1/+2
	git clean always excludes git clone subdirs; furthermore, even if I supply a dir as -e, the contents of that dir still get cleaned out. So it is useless to pass -e on the commandline. Drop it. Change-Id: I2b59cc9c9adf88a2663469b22cfeffbd66b5bf2e
2018-02-27	osmo-clean-workspace: fix force checkout of a subdirectory	Alexander Couzens	1	-2/+2
	Instead of the subdirectory, the main repository was forced checked out. Change-Id: If23e89872edf48dc5b751b3c069faf585bd6a3ef
2017-10-27	add osmo-clean-workspace.sh, use in osmo-deps.sh	Neels Hofmeyr	1	-0/+42
	So far, each jenkins job does its own cleanup, more or less well. Also, jenkins git config offers the 'Clean before checkout' option, which seems to fail when there are non-writable leftovers from a failed 'make distcheck'. Furthermore, our jenkins build slaves have unused compiled binaries piling up by the gigabytes: each matrix build x each parallel build and each compiled dependency therein builds .o, .a, .so and executables plus installs them to a local prefix, and just leaves them sitting around to rot until the job runs again. Instead, we want to clean them out when building is done. All of this calls for a unified cleanup script that knows how to clean a workspace properly, to run once before and once after each jenkins build. Here it is. Use that function in osmo-deps.sh instead of duplicating cleanup steps. Change-Id: I2409b2928b4d7ebbd6c005097d4ad7337307dd93