Started by an SCM change3097ac0902cd740139b0d1cfdbd90179de7379d28837ac0902cd740139b0d1cfdbd90179de7379d2883refs/remotes/origin/osmith/wip-dahdi7ac0902cd740139b0d1cfdbd90179de7379d28837ac0902cd740139b0d1cfdbd90179de7379d2883refs/remotes/origin/osmith/wip-dahdi3225c158b326abe394a731094b197ef8ff08e0196225c158b326abe394a731094b197ef8ff08e019622refs/remotes/origin/master5c158b326abe394a731094b197ef8ff08e0196225c158b326abe394a731094b197ef8ff08e019622refs/remotes/origin/master5c158b326abe394a731094b197ef8ff08e0196225c158b326abe394a731094b197ef8ff08e019622refs/remotes/origin/mastergit://git.osmocom.org/docker-playgroundfalse#3221284255update-osmo-ci-on-slaves-dp #322322falsefalse322677019SUCCESS1644825967617https://jenkins.osmocom.org/jenkins/view/SDR/job/update-osmo-ci-on-slaves-dp/322/gtp0-deb9buildcommon/pipeworkjenkins-common.shttcn3-ggsn-test/jenkins.shttcn3-fr-test/jenkins.sh5c158b326abe394a731094b197ef8ff08e0196221644825387000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.detreewide: fix missing --rm for "docker run" Add "--rm" to each "docker run" command, so they don't continuously fill up disk space. Fix this even in the pipework script. We don't use the code path there, but by always having --rm after "docker run" (same line or next line), a new lint script in osmo-ci I8ab9c291504475d670bdefc50c4524c5bdd4c880 can help us avoid this in the future. In ttcn3-ggsn-test/jenkins.sh, move one existing --rm in a later line upwards so the linter can find it. Related: SYS#5827, OS#5099 Related: https://github.com/jpetazzo/pipework/pull/248 Change-Id: I48b01c43fedf379b8a565eaab0369806d7831bd8 2022-02-14 08:56:27 +01005c158b326abe394a731094b197ef8ff08e019622treewide: fix missing --rm for "docker run"editttcn3-fr-test/jenkins.sheditjenkins-common.sheditttcn3-ggsn-test/jenkins.sheditcommon/pipeworkgithttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith