From cd64be2cea125b22e346199dcf20bb5ecf0ecd67 Mon Sep 17 00:00:00 2001 From: Oliver Giles Date: Sat, 27 Jun 2020 10:20:37 +1200 Subject: [PATCH] UserManual: add a note that env vars are not shell-expanded resolves #120 --- UserManual.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/UserManual.md b/UserManual.md index d8e418a..6109cf7 100644 --- a/UserManual.md +++ b/UserManual.md @@ -521,7 +521,7 @@ DUT_IP=192.168.3.2 FOO=bar ``` -This environment will then be available the run script of jobs associated with this context. +This environment will then be available the run script of jobs associated with this context. Note that these definitions are not expanded by a shell, so `FOO="bar"` would result in a variable `FOO` whose contents *include* double-quotes. --- @@ -680,6 +680,8 @@ Laminar will also export variables in the form `KEY=VALUE` found in these files: - `contexts/$CONTEXT.env` - `jobs/$JOB.env` +Note that definitions in these files are not expanded by a shell, so `FOO="bar"` would result in a variable `FOO` whose contents *include* double-quotes. + Finally, variables supplied on the command-line call to `laminarc queue`, `laminarc start` or `laminarc run` will be available. See [parameterized runs](#Parameterized-runs) ## laminarc