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

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • fitnesse-plugin
    • None
    • 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...

          [JENKINS-13696] Fitnesse should run on the slave of the build, not on the head node

          Frank Cornelissen created issue -
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 144163 ] New: JNJira + In-Review [ 176093 ]
          jaruzafa made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Fixed but Unreleased [ 10203 ]
          jaruzafa made changes -
          Status Original: Fixed but Unreleased [ 10203 ] New: Resolved [ 5 ]

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

              Created:
              Updated:
              Resolved: