Hello, I am trying to put together a jenkins system that is hosted on AWS through docker-cloud. I have created a few stacks that have the modules that I might want to test against (mongo, rabbit, etc). The Jenkins master is also running on its own stack. I wrote two scripts, one on the master (called start_slave.sh) and the other on the slave (called phone_home.sh). start_slave using the docker-cloud cli (installed on the master) to spin up a selected stack. The last thing the start_slave script does is issue a docker-cloud exec (https://docs.docker.com/apidocs/docker-cloud/#execute-command-inside-a-container) command that launches phone_home.sh on the slave. The phone_home script basically just downloads and launches the slave.jar. When I run start_slave from a terminal on the master, the slave.jar file appears to launch as expected (I get the information about how I'm not using it right, then it goes into spittting out mime code to the stdout. I'm guessing this is what it is supposed to look like?), but when I try to run the container as part of a dummy node startup script, the logs show the connection just hanging after the launch of phone_home. My question is this: Is there something I'm missing about launching the slave.jar from inside a container? Am I doing this correctly? I've also tried to launch the stack by mounting the docker socket in both the slave and master, using curl to issue api commands and the docker plugin. None of these seem to work but except for the plugin are more docker issues if I can't get this to work. Thanks!
-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/162787d8-cd33-431f-82b9-c617ada5ac43%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
