Jesse, Thanks for that link. The remote terminal is pretty slick, but it appears to not directly interact with the build sequence. It just opens a new terminal in the same directory on the slave and doesn't interact with the jenkins build sequence directly.
Kyle On Monday, April 15, 2013 3:09:29 PM UTC-4, Jesse Farinacci wrote: > > Greetings, > > On Mon, Apr 15, 2013 at 2:09 PM, Kyle Leber <[email protected]<javascript:> > > wrote: > >> What I would like to do (if possible) is combine the two somehow and use >> Jenkins to manage running of an interactive script on a test computer. This >> would allow me to leverage Jenkins' ability to consistently spawn scripts >> on a test computer and archive artifacts and console output history >> indefinitely. The part I'm not sure about is how to allow a user to >> interact with a Jenkins job that is in progress. Does anyone have any >> experience with this or know if it is possible? >> > > https://wiki.jenkins-ci.org/display/JENKINS/Remote+Terminal+Access+Plugin > > -Jesse > > -- > There are 10 types of people in this world, those > that can read binary and those that can not. > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
