Rob, thanks for the response. I do realize this is outside the realm of typical Jenkins applications. I'm such a huge fan of the way Jenkins can archive artifacts and log console activity that I'm trying to fit my square peg in a round hole. I will look into the GUI option to pop up a "yes/no" dialog. I think my idea with screen may work as well. It looks like I can spawn a screen session from within Jenkins that the local terminal can connect to (with the -x option) in order to response to prompts.
Kyle On Monday, April 15, 2013 2:18:16 PM UTC-4, Mandeville, Rob wrote: > > I think that what you’re asking for isn’t really what Jenkins does. I > don’t think that users can interact with a Jenkins job _*through Jenkins*_, > except to kill it. I think that you’ll have to have something in the job > reach out to the user. > > > > If the job you’re running is on Linux, can you get it to connect to the X > server that the technician is watching? Write a simple GUI in your > favorite language that just pops up a dialog on that X server and exits out > when somebody clicks OK (or exits nonzero when somebody clicks CANCEL). > Have one of your build steps run the GUI as a normal build step. The build > will hang, waiting for the techie to close the dialog, then go on after the > techie has done the manual part. > > > > --Rob > > > > *From:* [email protected] <javascript:> [mailto: > [email protected] <javascript:>] *On Behalf Of *Kyle Leber > *Sent:* Monday, April 15, 2013 2:09 PM > *To:* [email protected] <javascript:> > *Subject:* Can a user interact with an active Jenkins job? > > > > Note: this question also posted to stackoverflow here: > http://stackoverflow.com/questions/16021333/is-there-a-way-to-use-jenkins-to-run-an-interactive-test-script-and-have-a-user > > > > I have some hardware components I'm looking to test in a semi-automated > fashion. This will involve procedural steps similar to: > > 1. Prompt user to connect signal A to connector J1 > 2. After user confirms this is in place, automatically check for > successful signal detection > > I have experience writing such tests using bash, python, etc. I have also > used Jenkins to manage builds and automated tests. 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? > > This is on a Linux system, so maybe I can run it in a 'screen' session > that the user could attach to? > > Thanks, > Kyle > > -- > 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] <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > > > The information in this message is for the intended recipient(s) only > and may be the proprietary and/or confidential property of Litle & Co., > LLC, and thus protected from disclosure. If you are not the intended > recipient(s), or an employee or agent responsible for delivering this > message to the intended recipient, you are hereby notified that any use, > dissemination, distribution or copying of this communication is prohibited. > If you have received this communication in error, please notify Litle & Co. > immediately by replying to this message and then promptly deleting it and > your reply permanently from your computer. > -- 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.
