2012/4/29 Sami Tikka :
> At this point I bow my head in front of all this simplicity and go read the
> man page of the shell to find out where I have to place commands I want
> executed for all shells, not just interactive login shells. (.bashrc?)
Now that I actually looked into it instead of tr
The simplest way for Jenkins to get an interactive shell is to simply perform
an interactive login, just like you do when you type "ssh slavehost". I.e. to
omit the command to start the slave.
Other than that, Jenkins has little control over the way the sshd of the remote
host starts the shell
I have a Linux machine that uses user account A. User account
A's .profile file loads all sorts of useful environment variables.
I've tried to set up this machine as a Jenkins slave using the Launch
slave agents on Unix machines via SSH option:
https://wiki.jenkins-ci.org/display/JENKINS/Distrib
