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.

Sauce OnDemand plugin

View this plugin on the Plugins site

sauce: Sauce

  • credentialsId : String

sauceconnect: Sauce Connect

  • options : String (optional)
  • sauceConnectPath : String (optional)
  • useGeneratedTunnelIdentifier : boolean (optional)
  • useLatestSauceConnect : boolean (optional)
  • verboseLogging : boolean (optional)

saucePublisher: Run Sauce Labs Test Publisher

This step will trigger jenkins to parse the output of your build for SauceOnDemandSessionID lines and will attempt to update the job on sauce labs with the proper status. See the Sauce Labs wiki for more information
  • testDataPublishers (optional)
      Array / List of Nested Choice of Objects
    • attachments
      • $class: 'AutomateTestDataPublisher'
        • $class: 'ClaimTestDataPublisher'
          • displayClaimActionsInTestResultsTable : boolean
        • $class: 'JUnitFlakyTestDataPublisher'
          • jiraTestResultReporter
            • configs
                Array / List of Nested Choice of Objects
              • jiraSelectableArrayField
                • fieldKey : String
                • values
                    Array / List of Nested Object
                  • value : String
              • jiraSelectableField
                • fieldKey : String
                • value : String
              • jiraStringArrayField
                • fieldKey : String
                • values
                    Array / List of Nested Object
                  • value : String
              • jiraStringField
                • fieldKey : String
                • value : String

                  Insert a string value.

                  You can include Jenkins Environment variables (see link), or the following variables defined by this plugin:

                  Variable usage: ${VAR_NAME}

                  CRFL - new line

                  DEFAULT_SUMMARY - configured in the global configuration page

                  DEFAULT_DESCRIPTION - configured in the global configuration page

                  TEST_RESULT

                  TEST_NAME

                  TEST_FULL_NAME

                  TEST_STACK_TRACE

                  TEST_ERROR_DETAILS

                  TEST_DURATION

                  TEST_PACKAGE_NAME

                  TEST_PACKAGE_CLASS_METHOD_NAME

                  TEST_STDERR

                  TEST_STDOUT

                  TEST_OVERVIEW

                  TEST_AGE

                  TEST_PASS_COUNT

                  TEST_SKIPPED_COUNT

                  TEST_FAIL_SINCE

                  TEST_IS_REGRESSION - expands to true/false

                  BUILD_RESULT

                  WARNING: Your input will not be validated against the server's metadata. Check Jira to make sure you insert a valid value for this field and use the Validate Fields button bellow, otherwise the plugin will fail to create your issue.

              • jiraUserField
                • fieldKey : String
                • value : String

                  Insert the username.

                  For example if you have a user with:

                  Display Name: John Doe, Username: johndoe, Email: johndoe@email.com,

                  you need to write johndoe in this field. Any other value (like display name, or email) will not work.

            • projectKey : String
            • issueType : String
            • autoRaiseIssue : boolean
              Create issues automatically for failing tests that don't yet have one linked.
            • autoResolveIssue : boolean
              Automatically apply transition to resolve issues linked to tests, if the test passes.
              Experimental feature: For now it only looks for the first transition that contains in its name "resolve". If it is found, it will be applied, if not, the status of the issue will not change. In future releases this will be parametrized.
            • autoUnlinkIssue : boolean
            • overrideResolvedIssues : boolean
              Create issues automatically for failing tests that are linked to resolved issues in JiraIssueKeyToTestMap.json.
            • additionalAttachments : boolean (optional)
          • $class: 'JunitResultPublisher'
            If checked, each JUnit test result XML file will be examined to see if it represents a SOASTA CloudTest composition. For applicable tests, a hyperlink to the SOASTA CloudTest dashboard will be inserted into the test report.
            • urlOverride : String
              Specify the CloudTest URL to use when creating hyperlinks to CloudTest dashboards. Normally, this can be left blank, and the URL will be extracted from the test result file.
          • $class: 'PerfSigTestDataPublisher'
            • dynatraceProfile : String
          • $class: 'SahaginTestDataPublishser'
            • $class: 'SauceOnDemandReportPublisher'
              Show embedded Sauce OnDemand reports, including video and logs. Your test should use Selenium client factory (at least version 1.3 to match test cases to individual Sauce OnDemand jobs).
              • jobVisibility : String (optional)
                Set your test results visibility permissions. The Sauce Documentation has all the various levels described in detail.
            • $class: 'StabilityTestDataPublisher'
              • $class: 'TestCafePublisher'
                • $class: 'TestReporter'
                  • $class: 'YoutrackTestDataPublisher'

                  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.