Jenkins fitnesse build aborts after HTTP Timeout is exceeded, but tests continue to run

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: fitnesse-plugin
    • None
    • Environment:
      Jenkins ver. 1.446
      Hudson Fitnesse plugin 1.4

      To reproduce:
      1. Start Fitnesse on a target machine
      2. Setup a Jenkins job to build using the 'Fitnesse instance is already running' option
      3. Set the 'HTTP Timeout (ms)' to a value which will cause the test to timeout

      Result:
      > Jenkins build is classed as Aborted when the timeout value is exceeded, however the Fitnesse tests on the target machine continue to run

      Expected Result:
      > Jenkins build failing or aborting should force Fitnesse for stop tests

            Assignee:
            Unassigned
            Reporter:
            Ashok Manji
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: