Hi All, Is there a way to start slave.jar so that it will process just one job and then exit when the job ends (either via success, failure or user abort)?
I am currently prototyping. slave.jar runs (with -jnlpUrl) on Windows 2003. slave.jar runs from the command line (that may change as I get closer to production, for prototyping, the command line is good enough). This is windows, and some of the processes started are GUI programs, so I'm probably stuck with using the command line moving forward. The reason I'm looking for a command line parameter to force the slave.jar to exit when done processing one job is to debug/isolate a problem I'm seeing with my master-slave setup. When a job running on the slave is aborted (either at the browser via jenkins job control UI) or by the build timeout plugin, some commands started by batch files don't exit (they keep running). The legacy tasks being run have hardcoded file locations. It'd take a lot of effort to modify the system so that it could work with relative paths (i.e., writing all files into the workspace instead of into D:\[HARDCODED_DIRECTORY]). Because of the hardcoded paths, when my job tries to clear the D:\HARDCODED_DIRECTORY so it can start with a clean slate (svn co, etc), previous processes that have that directory as their current working directory prevent removal of the directory. There are other side effects, but that's a major one. I could get the source to jenkins and patch the feature in, I guess, but if the feature is already in there I'd rather not reimplement it :-). Many thanks. Gerald Quimpo -- Gerald Timothy Quimpo bopolissimus_at_gmail.com http://bopolissimus.*b*l*o*g*s*p*o*t*.com "(Postgresql) Cursors are biased towards fast-start plans on the theory that you may not be intending to fetch the whole result. Queries with ORDER BY and/or LIMIT are particularly likely to see plan changes as a consequence of that."
