Sigh. Deep down, I was afraid of this...unfortunately, we don't have the option of switching to a more modern environment.
On Wed, Jan 9, 2013 at 9:32 AM, Mandeville, Rob <[email protected]>wrote: > The master is a WAR, the slave is a JAR. You need Java installed on > both ends.**** > > ** ** > > If you’re really hard up, can you run the slave on a saner build > environment and just write all the build steps to do things like “ssh > {hostname} {command you need to run}”?**** > > ** ** > > --Rob**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *[email protected] > *Sent:* Wednesday, January 09, 2013 10:20 AM > *To:* [email protected] > *Subject:* Jenkins Usage Question - Java requirement**** > > ** ** > > Hello, > > We have an old build environment where the build server does not support > Java. > > Given this limitation, is it possible to still use Jenkins in a > master/slave set up? Or do both master/slave require Java? > > Any pointers are appreciated. > > Thank you. > Amad**** > 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. >
