Enable fitness plugin to run on Jenkins distributed slave agent

[gkarpinski]

Each agent declared in jenkins admin configuration must have an environment variable : HOST_NAME with host name of the slave node.

FitnesseExecutorTest.java isn't very clean ... i disable the test with the host.

I use this plugin ( my branche on GITHub ) in a 3 distributed slaves configuration, and with some job that need remote deployement before testing, with ssh.

it works :)

[swestcott]

@gkarpinski Some tests are failing since I merged this onto master. Can you take a look? Also, what effort would be need to fix the tests that you commented out?

Broken build,
https://swestcott.ci.cloudbees.com/job/Jenkins%20Fitnesse/org.jenkins-ci.plugins$fitnesse/14/testReport/

[gkarpinski]

@swestcott Sorry but i used the skiptest flag at true... I will take a look this week for the NPE in test, and also for commented line ( so for 05/25/12) .

[kurt-wang]

Hi,
I just upgraded the plug-in to v1.8. I don't see any difference in the interface when setting up a Jenkins multi-configuration project. And I am not sure how the job can be assigned to any slave.

Would I just use environment variable ${HOST_NAME} as the host name for FitNesse and it would read it from any slave machine that runs the test?

Thanks.

[sbellus]

I set HOST_NAME for jenkins slave that I use for job that triggers and publish Fitnesse test.
The Fitnesse plugin still connects from Jenkins master towards Fitnesse. I check log in Fitnesse.

Am I missing something?