Details
-
Suggestion
-
Resolution: Tracked Elsewhere
-
None
-
None
Description
A customer has requested that the Bamboo/Clover plugin track coverage per-committer.
This could work as follows:
- a build is triggered by a commit
- bamboo builds, and a clover.xml is produced
- a post build plugin (possibly part of the clover plugin?) could extract who changed which source file from the SCM
- the plugin then queries the clover.xml for the coverage of each file and records that number against the committer
- a report is generated that shows each committer's %coverage
There are some problems with this, for example:
- how to handle multiple committers of the same file in any particular build
- if committer X modifies file F, but committer Y modifies test T that covers X - committer X is attributed with the coverage for X (clover per-test coverage could help here)
Attachments
Issue Links
- blocks
-
BAM-4048 Improve Clover-Bamboo Plugin
- Closed