Fitnesse should run on the slave of the build, not on the head node

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • Component/s: fitnesse-plugin
    • None
    • Environment:
      Distributed builds

      The setup I use for jenkins is to have a single non building head node, and several build slaves. In this case, the jenkins fitnesse plugin tries to run fitnesse on the head node instead of the slave the build is running on.. Attached is the fix I applied locally...

            Assignee:
            Unassigned
            Reporter:
            Frank Cornelissen
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: