[ci] Quote uses of path variables since it may contain spaces#10306
[ci] Quote uses of path variables since it may contain spaces#10306ycombinator wants to merge 14 commits intoelastic:masterfrom ycombinator:quote-docker-volume
Conversation
PWD since it may contain spaces
|
There are more usages for |
PWD since it may contain spaces|
I see the double quoting issue causing the latest failures. I just need to run a couple of errands over the next couple hours so will get back to this PR after that. |
generator/beat/{beat}/Makefile
Outdated
| BEAT_NAME={beat} | ||
| BEAT_PATH={beat_path} | ||
| BEAT_GOPATH=$(firstword $(subst :, ,${GOPATH})) | ||
| BEAT_GOPATH=$(firstword $(subst :, ,"${GOPATH}")) |
There was a problem hiding this comment.
Only the stuff that gets passed to the shell will need quoting. So it's probably best to only quote on the shell side (where the variables are used) for consistency. Otherwise you'll end up with double quoting.
For example
TEST="TEST"
echo:
echo "${TEST}"
$ make echo
echo ""TEST"" <- The executed command has double quotes.
|
@andrewkroh I've tried a few different ideas to preserve spaces in the That's probably because I'm running out of ideas on how to preserve the space in the |
|
Closing this PR unmerged for now as the original Infra change was reverted for now. |
Our Jenkins CI setup recently introduced configuration changes that cause " && " to be included in the workspace path. This is causing failures like:
This PR attempts to quote several paths used by our CI jobs so as to preserve the " && " in the paths as-is, and not be interpreted.