It is a normal master-slave connection, just like any other slave. As far as I
know, until very recently, there was *no* mechanism to transfer credentials
from the master to a slave as-needed. Slaves have always needed to have any
necessary credentials setup before the master sent them work to d
Thanks for the explanation. I had assumed that the EC2 plugin connected the
EC2 instance to the master Jenkins as a normal slave, so that from that
point on the standard Jenkins slave communication would remain the same.
Does all the normal information from a build go back to the master with the
The Amazon EC2 plugin is not 'credentials aware' at this point, so it's not
going to push credentials down to the slave. This is something I plan to work
on in the near future, but I've been waiting for the Credentials plugin and its
data structures to settle down.
As it stands today, the EC2 s
I see that GIT_SSH is an environment variable which changes the command
which Git uses to connect to the remote host. Maybe this is the wrong path
to search down, but is how can I find out what this value is? Or perhaps
what dependencies it might have. Maybe the AMI is missing something that I
I'm trying to use the Jenkins Amazon EC2 plugin to start and use AWS EC2
instances for slaves. Jenkins will start the slave, and the slave connects
to the master, but my builds are not able to connect to our Git
repositories over SSH. The slave is running on the Amazon Linux AMI.
I created a Gl
