Inspired by the GitHub Checks API, this plugin aims to provide a general API to allow Jenkins plugins publishing checks (or reports) to remote source code management (SCM) platforms (e.g. GitHub, GitLab, BitBucket, etc.).
By consuming this API, other plugins can publish check with customized parameters for a Jenkins build, such as status, summary, warnings, code annotations, or even images. Implementations of this API decide on how to make use of these parameters and where to publish the checks.
- Warnings Next Generation Plugin
- Code Coverage API Plugin
- JUnit Plugin - since 1.39
- Autograding Plugin
This plugin, along with it's GitHub implementation, has been installed on ci.jenkins.io to help maintain over 1500 Jenkins plugins. You can take a look at the action for this repository or other plugin repositories under Jenkins organization for the results.
Build Status Check
This plugin defines extension points to publish statuses to different SCM platforms.
It depends on the implementation to decide whether to skip them and what name to use.
If enabled, the statuses will be published in different stages of a Jenkins build (enters the queue, checkout, and completes).
Instead of depending on consumers plugins, the users can publish their checks directly in the pipeline script:
publishChecks name: 'example', title: 'Pipeline Check', summary: 'check through pipeline', text: 'you can publish checks in pipeline script', detailsURL: 'https://github.com/jenkinsci/checks-api-plugin#pipeline-usage'
Refer to our contribution guidelines
Licensed under MIT, see LICENSE