Mads Jon Nielsen
Mads Jon Nielsen
You will have to come up with some sort of custom cli options or argument parsing. It would be hard to implement a `job-*` solution. Since an actual job name...
That would be a good cli option yeah.
`gitlab-ci-local --env-from-host "SOME_ENV_VAR" --env-from-host "SOME_OTHER"` ```` # .gitlab-ci-local-env ENV_FROM_HOST=SOME_ENV_VAR,SOME_OTHER ```` Marking this as a feature request.
@ANGkeith People have all sorts of `export` in their `.bashrc` and they just want an easy way to pass these values to jobs, i think
@mcintyre321 When running shell-executor jobs, you need to use the `--shell-isolation` option to prevent your hosts variables from entering the job, unless you have them in `.bashrc` ofcourse.
Yeah, that flag is not implemented, marking as feature
@dxh9845 Have you timed that these changes are actually faster than current version? Also, jest and eslint jobs are failing.
Please provide `bash --version`
Please paste output from `rsync --version`
And from which PC/Server or VM do you execute your `gitlab-ci-local` command, when this error happens?