The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.

For a list of other such plugins, see the Pipeline Steps Reference page.

Team Foundation Server Plug-in

step([$class: 'TeamCollectResultsPostBuildAction']): Collect results for TFS/Team Services

At the end of the build, files matching each of the requested result types will be archived for retrieval by TFS/Team Services.
  • requestedResults (optional)
      Array/List
      Nested Object
    • teamResultType
      • Values: JUNIT, NUNIT, VS_TEST, XUNIT, COBERTURA, JACOCO
    • includes (optional)
      Enter a comma-separated list of file patterns to collect the files relevant to the selected result type. Examples:
      • **/target/surefire-reports/TEST-*.xml, **/target/failsafe-reports/TEST-*.xml
      • reports/jacoco.exec
      • **/TestResults/*.xml
      • Type: String

step([$class: 'TeamCompletedStatusPostBuildAction']): Set build completion status in TFS/Team Services

At the end of the build, the status of the associated pull request and/or commit will be updated in TFS/Team Services with the results of the build, including a link back to the Jenkins build.

    step([$class: 'TeamPendingStatusBuildStep']): Set build pending status in TFS/Team Services

    The status of the associated pull request and/or commit will be updated in TFS/Team Services as "pending", including a link back to the Jenkins build.
      At the end of the build, if any work items in TFS/Team Services have been found to be associated with the Jenkins build, a hyperlink back to the Jenkins build will be added to the affected work items.

        Was this page helpful?

        Please submit your feedback about this page through this quick form.

        Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?

            


        See existing feedback here.