Put a slave node on host B (see https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds) and tell your job to run only on the slave on B.
If you need to run the build on A, then you’ll need a way to get the build.xml from B to A. You could enter a copy of build.xml into your SCM (you are using source control, right?), and use an SCM plugin to pull it in. Whether you run your build on B or A, the output log is readable by the server (slaves pipe their standard output to the server), so the TestNG plugin should work on your server on A even if you’re building on B. --Rob From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of zw Sent: Monday, July 02, 2012 2:07 PM To: jenkinsci-users@googlegroups.com Subject: Hudson remote build job kick off Hi All I have host A running the Hudson server. I have another host B with its Ant build.xml there in host B. How do I configure Hudson on host A to kick off the build.xml in host B. If this is not possible, what are the workarounds, possible solutions to this problem. If this is possible, how do I configure the post-action report for it in Hudson job to display the testng test results. I have testng plugin installed on Hudson server on host A already. Any help is appreciated. Thanks 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.
