Details
-
Bug
-
Resolution: Tracked Elsewhere
-
Low
-
None
-
8.1.2
-
None
-
1
-
Severity 3 - Minor
-
Description
Issue Summary
When setting AcceptEnv in ~/.ssh/config, Bamboo doesn't apply the settings there. This happens because Bamboo doesn't call the OS native SSH client, but uses a built-in plugin
Steps to Reproduce
- Create a file in the users profile:
touch ~/.ssh/config chmod 600 config
- Set a rule, like for example:
Host * SendEnv bamboo*
- In the remote server, set /etc/ssh/sshd_config to accept those variables:
... # Allow client to pass locale environment variables AcceptEnv bamboo* AcceptEnv LANG LC_* ...
- In a build, set a variable:
var = value1
- Create a SSH task and use the variable:
echo ${bamboo_var}
Expected Results
Value is printed
Actual Results
Value is not printed. This is also reproducible by defining the variable on a script task:
export bamboo1=value1
Similar tests run from command line (same computer + OS user) work normally (those same variables can be echoed).
Workaround
Use a script task instead.
Attachments
Issue Links
- relates to
-
BAM-21592 SSH tasks won't parse variables when using underscores instead of dots.
- Closed