Started by an SCM change303290df47815bc0b8a2aac06215aaab29587eef453290df47815bc0b8a2aac06215aaab29587eef453refs/remotes/origin/master290df47815bc0b8a2aac06215aaab29587eef453290df47815bc0b8a2aac06215aaab29587eef453refs/remotes/origin/master290df47815bc0b8a2aac06215aaab29587eef453290df47815bc0b8a2aac06215aaab29587eef453refs/remotes/origin/mastergit://git.osmocom.org/docker-playgroundfalse#3031313255update-osmo-ci-on-slaves-dp #303303falsefalse303664654SUCCESS1643461268515https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/303/gtp0-deb9build- ttcn3-pgw-test/jenkins.sh290df47815bc0b8a2aac06215aaab29587eef4531643460848000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.dettcn3-pgw-test: fix jenkins.sh: do not use bash specific syntax
On some systems /bin/sh is a symbolic link to bash, so everything
works fine. On systems where /bin/sh is a real sh, copy fails:
cp: cannot access 'open5gs-{smf,upf,nrf}.yaml': No such file or directory
Change-Id: I64e9ddefdb6deb21b3bce3bc1af875a92919e6c9
Related: SYS#5602
2022-01-29 18:54:08 +0600290df47815bc0b8a2aac06215aaab29587eef453ttcn3-pgw-test: fix jenkins.sh: do not use bash specific syntaxeditttcn3-pgw-test/jenkins.sh
githttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiy