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

FitNesse Plugin should be usable in a Jenkinsfile

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • fitnesse-plugin
    • None

      The FitNesse Plugin should be usable in the Jenkinsfile or other Jenkins Pipeline definitions.
      (For me, this is kind of a blocker)

          [JENKINS-41514] FitNesse Plugin should be usable in a Jenkinsfile

          as pointed out in PR30

          Code changes made only adresses compatible code so the step can be used as a generic task as like

          step([
            $class: 'FitnesseResultsRecorder',
            fitnessePathToXmlResultsIn: '*.xml'
          ])
          

          but it doesn't address the DSL as far I can see

          Marcel 'childNo͡.de' Trautwein added a comment - - edited as pointed out in PR30 Code changes made only adresses compatible code so the step can be used as a generic task as like step([ $class: 'FitnesseResultsRecorder' , fitnessePathToXmlResultsIn: '*.xml' ]) but it doesn't address the DSL as far I can see

          jaruzafa added a comment -

          Fixed in 1.24

          jaruzafa added a comment - Fixed in  1.24

            Unassigned Unassigned
            moerg Marc Jegliewski
            Votes:
            6 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: