The following pipeline will run
test.sh jobs in parallel, and then process all the resulting JUnit XML files to create a summary build annotation.
steps: - command: test.sh parallelism: 50 artifact_paths: tmp/junit-*.xml - wait: ~ continue_on_failure: true - plugins: - junit-annotate#v1.9.0: artifacts: tmp/junit-*.xml
The artifact glob path to find the JUnit XML files.
The regular expression (with capture group) that matches the job UUID in the junit file names. This is used to create the job links in the annotation.
To use this, configure your test reporter to embed the
$BUILDKITE_JOB_ID environment variable into your junit file names. For example
This setting controls the format of your failed test in the main annotation summary.
There are two options for this:
MyClass::UnderTest text of the failed expectation in path.to.my_class.under_test
MyClass::UnderTest text of the failed expectation in path/to/my_class/under_test.file_ext
If this setting is true and any errors are found in the JUnit XML files during parsing, the annotation step will exit with a non-zero value, which should cause the build to fail.
The buildkite annotation context to use. Useful to differentiate multiple runs of this plugin in a single pipeline.
Include the specified number of slowest tests in the annotation. The annotation will always be shown.
To test the plugin hooks (in Bash) and the junit parser (in Ruby):
docker-compose run --rm plugin && docker-compose run --rm ruby
To test the Ruby parser locally:
cd ruby rake
To test your plugin in your builds prior to opening a pull request, you can refer to your fork and SHA from a branch in your
steps: - label: Annotate plugins: - YourGithubHandle/junit-annotate#v1.9.0: ...
MIT (see LICENSE)