-
Task
-
Resolution: Fixed
-
Minor
-
None
Idea: simplify Cobertura plugin by using APIs and features provided by Code Coverage API Plugin.
Idea:
- Cobertura plugin benefits from features we offer in the plugin
- There is no breaking changes
- jeffpearce proposed to implement reporter and deprecate/remove old data model
- Oleg: Migration logic for existing data
Acceptance criteria:
- Transparent to users:
- cobertura() Pipeline step and Cobertura Build Step start contributing to Code Coverage API data model
- existing data is compatible or automatically migrated
We need to design this ticket. Open questions:
- How do we implement it? Maybe switches to enable API/UI? Duplicate data in the in-memory model? ...
- Could we simplify the data model somehow
- Which parts of Cobertura plugin do we deprecate?
[JENKINS-51424] Prototype integration between Code Coverage API and Cobertura plugin
Description |
New:
Idea: simplify Cobertura plugin by using APIs and features provided by Code Coverage API Plugin. |
Description |
Original:
Idea: simplify Cobertura plugin by using APIs and features provided by Code Coverage API Plugin. |
New:
Idea: simplify Cobertura plugin by using APIs and features provided by Code Coverage API Plugin. Idea: * Cobertura plugin benefits from features we offer in the plugin * |
Description |
Original:
Idea: simplify Cobertura plugin by using APIs and features provided by Code Coverage API Plugin. Idea: * Cobertura plugin benefits from features we offer in the plugin * |
New:
Idea: simplify Cobertura plugin by using APIs and features provided by Code Coverage API Plugin. Idea: * Cobertura plugin benefits from features we offer in the plugin * There is no breaking changes |
Description |
Original:
Idea: simplify Cobertura plugin by using APIs and features provided by Code Coverage API Plugin. Idea: * Cobertura plugin benefits from features we offer in the plugin * There is no breaking changes |
New:
Idea: simplify Cobertura plugin by using APIs and features provided by Code Coverage API Plugin. Idea: * Cobertura plugin benefits from features we offer in the plugin * There is no breaking changes * [~jeffpearce] implement reporter? * Oleg: Migration logic for existing data |
Description |
Original:
Idea: simplify Cobertura plugin by using APIs and features provided by Code Coverage API Plugin. Idea: * Cobertura plugin benefits from features we offer in the plugin * There is no breaking changes * [~jeffpearce] implement reporter? * Oleg: Migration logic for existing data |
New:
Idea: simplify Cobertura plugin by using APIs and features provided by Code Coverage API Plugin. Idea: * Cobertura plugin benefits from features we offer in the plugin * There is no breaking changes * [~jeffpearce] proposed to implement reporter and deprecate/remove old data model * Oleg: Migration logic for existing data |
Description |
Original:
Idea: simplify Cobertura plugin by using APIs and features provided by Code Coverage API Plugin. Idea: * Cobertura plugin benefits from features we offer in the plugin * There is no breaking changes * [~jeffpearce] proposed to implement reporter and deprecate/remove old data model * Oleg: Migration logic for existing data |
New:
Idea: simplify Cobertura plugin by using APIs and features provided by Code Coverage API Plugin. Idea: * Cobertura plugin benefits from features we offer in the plugin * There is no breaking changes * [~jeffpearce] proposed to implement reporter and deprecate/remove old data model * Oleg: Migration logic for existing data Acceptance criteria: * Transparent to users: ** cobertura() Pipeline step and Cobertura Build Step start contributing to Code Coverage API data model ** existing data is compatible or automatically migrated We need to design this ticket. |
Description |
Original:
Idea: simplify Cobertura plugin by using APIs and features provided by Code Coverage API Plugin. Idea: * Cobertura plugin benefits from features we offer in the plugin * There is no breaking changes * [~jeffpearce] proposed to implement reporter and deprecate/remove old data model * Oleg: Migration logic for existing data Acceptance criteria: * Transparent to users: ** cobertura() Pipeline step and Cobertura Build Step start contributing to Code Coverage API data model ** existing data is compatible or automatically migrated We need to design this ticket. |
New:
Idea: simplify Cobertura plugin by using APIs and features provided by Code Coverage API Plugin. Idea: * Cobertura plugin benefits from features we offer in the plugin * There is no breaking changes * [~jeffpearce] proposed to implement reporter and deprecate/remove old data model * Oleg: Migration logic for existing data Acceptance criteria: * Transparent to users: ** cobertura() Pipeline step and Cobertura Build Step start contributing to Code Coverage API data model ** existing data is compatible or automatically migrated We need to design this ticket. Open questions: * How do we implement it? Maybe switches to enable API/UI? Duplicate data in the in-memory model? ... * Could we simplify the data model somehow * Which parts of Cobertura plugin do we deprecate? |
Epic Link |
New:
|
Other approach:
Tricky thing: data cachiing