| The two products of Warnings seem to be
- annotations of files (coverage over the current commit state)
- summary numbers (a time-series snapshot of the current commit state)
- which can be differentiated from previous builds (`master`/last passing build)
If I'm correct about that, JEP203 wouldn't really be required, would it? It would be possible for Blue Ocean to support two highly broad and valuable views of the build/build trend
- file annotations (by category, which Warnings NG would have to report correctly)
- "This line of code reports an annotation produced by a lint tool."
- ...with the possible addition of a view of annotations produced by the tool, for acceptance and navigating the annotations
- ...with the possible addition of a view of annotations produced by all tools, for acceptance and navigating the annotations
- build trends
- only meaningful in build-trend contexts
- already a major part of Blue Ocean's interface
- for an individual build possibly related to a "main" branch build
Not a small ask, but I'm not sure it's as broad as "offer an open interface to extend Blue Ocean," which (IMHO) is quite the ask. |
