We should have a Drone status API that allows 3rd party system to annotate commits and link back to those 3rd party systems. This would be similar to the GitHub status API.
An example use case would be a coverage system. A coverage system would store detailed coverage metrics, but could provide Drone with a high-level status and link to those detailed coverage reports.
This came out of #239
bradrydzewski
All 6 comments
Just an FYI: https://github.com/badges/shields/issues/294 would really love this.
DavidJFelix
on 2 May 2015
:+1:
pine
on 24 Jul 2015
Would have liked to see this implemented. It'd be the only way to tie external services to the drone UI. Using a testresults or coverage 3rd party component is fine but with no way to actually link to a particular build the UX is going to be pretty poor.
cooperaj
on 31 Jan 2017
Coverage, test results, code quality, and links to external artifacts will be added natively to drone. Drone will provide an API for plugins to send this data back to drone during the build.
bradrydzewski
on 31 Jan 2017
Is this still being worked on? Is there another issue tracking progress?
dwilhel1
on 30 Apr 2020
We decided not to pursue native reporting in Drone. We instead recommend using Coveralls / Codecov for coverage, Artifactory / Sonatype Nexus / Archiva for artifacts, and tools like Hound / Codacy / Sonarqube / etc for code quality. Many of these tools already have plugins for Drone.
bradrydzewski
on 30 Apr 2020
Related issues
mvdan
路
6Comments
josmo
路
5Comments
Dentrax
路
5Comments
phil-davis
路
4Comments
bradrydzewski
路
5Comments
Most helpful comment
Coverage, test results, code quality, and links to external artifacts will be added natively to drone. Drone will provide an API for plugins to send this data back to drone during the build.