Skip to content
This repository has been archived by the owner. It is now read-only.

Enable fitness plugin to run on Jenkins distributed slave agent #8

Merged
merged 1 commit into from May 18, 2012

Conversation

Projects
None yet
5 participants
@gkarpinski
Copy link

gkarpinski commented May 15, 2012

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 :)

@brobie

This comment has been minimized.

Copy link

brobie commented on f7aea0e May 2, 2012

Is this something that you plan on making a pull request for? We would really love to have the fitnesse plugin run on the Jenkins slaves.

swestcott added a commit that referenced this pull request May 18, 2012

Merge pull request #8 from gkarpinski/master
Enable fitness plugin to run on Jenkins distributed slave agent

@swestcott swestcott merged commit 9be72fd into swestcott:master May 18, 2012

@swestcott

This comment has been minimized.

Copy link
Owner

swestcott commented May 18, 2012

@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

This comment has been minimized.

Copy link
Author

gkarpinski commented May 20, 2012

@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

This comment has been minimized.

Copy link

kurt-wang commented Jan 5, 2013

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

This comment has been minimized.

Copy link

sbellus commented Feb 11, 2014

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?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.