Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-13696

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

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: fitnesse-plugin
    • Labels:
      None
    • Environment:
      Distributed builds
    • Similar Issues:

      Description

      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...

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved: