Jenkins integration

Using the Plugin

Use the mabl Jenkins Integration Plugin to automatically trigger specific environment or application plans to run as a build stage.

See the plugin listing for full plugin details.

Visit the plugin repo to lodge issues, or fork and submit pull requests.

Plugin Results

Plugin results can be viewed in mabl or in the JUnit XML test output. JUnit tests are output to the reports.xml file in your Jenkins build directory after the mabl tests complete.

Using the Jenkins JUnit plugin you can expose the mabl results in Jenkins.

  1. Add a Run mabl tests action to your build
  2. Add a Publish JUnit test result report post-build action to your build
  3. Configure the Test report XMLs field with report.xml
  4. Check Do not fail the build on empty test results (empty if no tests ran)
Configured Jenkins mabl build action and JUnit test reporting

Configured Jenkins mabl build action and JUnit test reporting

You can now see your test results reported with your test runs under Test Result for each build.

Detailed view of mabl test runs via JUnit result output.

Detailed view of mabl test runs via JUnit result output.

Add deployment trigger to desired plans

Only plans with deployment triggers in their plan configurations will be run by the build step.

Updated about a month ago

Jenkins integration


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.