Commit 8d84c275 authored by Steve Azzopardi's avatar Steve Azzopardi

Remove unused bash scripts

These bash commands are not longer user by GitLab Runner.

reference #4013
parent a82377e8
#!/bin/sh
set -x
for path in $@; do
chmod 777 "$path"
done
#!/bin/sh
host=$(env | grep -m1 _TCP_ADDR | cut -d = -f 2)
port=$(env | grep -m1 _TCP_PORT | cut -d = -f 2)
if [ -z "$host" ] || [ -z "$port" ]; then
echo "No HOST or PORT"
exit 1
fi
echo -n "waiting for TCP connection to $host:$port..."
while ! nc -w 1 $host $port 2>/dev/null
do
echo -n .
sleep 1
done
echo 'ok'
......@@ -321,14 +321,13 @@ After the service is started, GitLab Runner waits some time for the service to
be responsive. Currently, the Docker executor tries to open a TCP connection to
the first exposed service in the service container.
You can see how it is implemented by checking [this script][service-file].
You can see how it is implemented by checking this [Go command](https://gitlab.com/gitlab-org/gitlab-runner/blob/master/commands/helpers/health_check.go).
## The builds and cache storage
The Docker executor by default stores all builds in
`/builds/<namespace>/<project-name>` and all caches in `/cache` (inside the
container).
You can overwrite the `/builds` and `/cache` directories by defining the
`builds_dir` and `cache_dir` options under the `[[runners]]` section in
`config.toml`. This will modify where the data are stored inside the container.
......@@ -616,7 +615,6 @@ This executor is no longer maintained and will be removed in the near future.
[toml]: ../commands/README.md#configuration-file
[alpine linux]: https://alpinelinux.org/
[special-build]: https://gitlab.com/gitlab-org/gitlab-runner/tree/master/dockerfiles/build
[service-file]: https://gitlab.com/gitlab-org/gitlab-runner/blob/master/dockerfiles/build/scripts/gitlab-runner-service
[privileged]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
[entry]: https://docs.docker.com/engine/reference/run/#entrypoint-default-command-to-execute-at-runtime
[secpull]: ../security/index.md#usage-of-private-docker-images-with-if-not-present-pull-policy
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment