Hi Rob

Also

When configuring for slave on host B, does the slave allow for xvnc plugin 
of Hudson so that xvnc could be started locally on host B ?
This is because the Selenium test scripts would kick off FF browser for 
testing and the Ant script keeps spewing out errors:

  [sshexec]    [testng] org.openqa.selenium.firefox.NotConnectedException: 
Unable to connect to host 127.0.0.1 on port 7055 after 45000 ms. Firefox 
console output:
  [sshexec]    [testng] Error: no display specified
  [sshexec]    [testng] Error: no display specified
  [sshexec] 
  [sshexec]    [testng]         at 
org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:101)
  [sshexec]    [testng]         at 
org.openqa.selenium.firefox.FirefoxDriver.startClient(FirefoxDriver.java:216)
  [sshexec]    [testng]         at 
org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:93)
  [sshexec]    [testng]         at 
org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:156)
  [sshexec]    [testng]         at 
org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:151)
  [sshexec]    [testng]         at 
org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:89)
  [sshexec]    [testng]         at framework.Browser$2.get(Browser.java:16)
  [sshexec]    [testng]         at 
framework.tests.AbstractWebTests.openWebSystem(AbstractWebTests.java:37)
  [sshexec]    [testng]         at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)
  [sshexec]    [testng]         at sun
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
  [sshexec]    [testng]         at sun
.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  [sshexec]    [testng]         at 
java.lang.reflect.Method.invoke(Method.java:616)
  [sshexec]    [testng]         at 
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:76)
  [sshexec]    [testng]         at 
org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525)
  [sshexec]    [testng]         at 
org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
  [sshexec]    [testng]         at 
org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130)
  [sshexec]    [testng]         at 
org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:173)
  [sshexec]    [testng]         at 
org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:105)
  [sshexec]    [testng]         at 
org.testng.TestRunner.runWorkers(TestRunner.java:1147)
  [sshexec]    [testng]         at 
org.testng.TestRunner.privateRun(TestRunner.java:749)
  [sshexec]    [testng]         at 
org.testng.TestRunner.run(TestRunner.java:600)
  [sshexec]    [testng]         at 
org.testng.SuiteRunner.runTest(SuiteRunner.java:317)
  [sshexec]    [testng]         at 
org.testng.SuiteRunner.runSequentially(SuiteRunner.java:312)
  [sshexec]    [testng]         at 
org.testng.SuiteRunner.privateRun(SuiteRunner.java:274)
  [sshexec]    [testng]         at 
org.testng.SuiteRunner.run(SuiteRunner.java:223)
  [sshexec]    [testng]         at 
org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
  [sshexec]    [testng]         at 
org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
  [sshexec]    [testng]         at 
org.testng.TestNG.runSuitesSequentially(TestNG.java:1039)
  [sshexec]    [testng]         at 
org.testng.TestNG.runSuitesLocally(TestNG.java:964)
  [sshexec]    [testng]         at org.testng.TestNG.run(TestNG.java:900)
  [sshexec]    [testng]         at 
org.testng.TestNG.privateMain(TestNG.java:1182)
  [sshexec]    [testng]         at org.testng.TestNG.main(TestNG.java:1146) 


On Monday, July 2, 2012 11:15:23 AM UTC-7, Mandeville, Rob wrote:
>
>  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.
>  

Reply via email to