I am not sure about using `shellescape` here. With the previous version of gitlab-ci-runner, I could have a line like this in my build script on the coordinator:

```
export foo="bar"; echo $foo
```

After shellescape, this becomes

```
export\ foo\=\"bar\"\;\ echo\ \$foo
```

If I put the first line in a bash script I get:

```
gigantor:tmp jacobvosmaer$ cat no_escape.bash 
export foo="bar"; echo $foo
gigantor:tmp jacobvosmaer$ bash no_escape.bash 
bar
```

```
gigantor:tmp jacobvosmaer$ cat escape.bash 
export\ foo\=\"bar\"\;\ echo\ \$foo
gigantor:tmp jacobvosmaer$ bash escape.bash 
escape.bash: line 1: export foo="bar"; echo $foo: command not found
```