Given we have pre-merge review, we need infrastructure to store files post-merge (e.g. code coverage). And then in 'test' and 'gate' jobs be able to compare results against that.
It would be nice to then be able to include freeform text report (summary or url) from the build into the jenkins-bot comment on Gerrit.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T101542 [EPIC] Provide pre-merge reports on patchsets (tracking) | |||
| Resolved | Krinkle | T101543 Provide (pre-merge) performance reports on patchsets | |||
| Stalled | None | T64633 Jenkins: Set up perceptual diffs (visual regression testing) | |||
| Declined | None | T72945 Preview generated documentation in test pipeline for review | |||
| Declined | None | T101545 Provide infrastructure to store files by project/branch post-merge to compare with pre-merge | |||
| Declined | None | T114998 Provide Swift object store(s) for the labs projects |
@Jdforrester-WMF thanks a ton for filling those tasks. With the current team workload that is probably not going to happen anytime soon though.
For the record, James filed this following a discussion with me about being able to have reports like "Code review: 85% ( 3%)" in the jenkins-bot comment on Gerrit.
The only thing being stored is a single result per project/branch, not for each patch set. (Patchset tests already include relevant data in the build output and artefacts, which don't need to be stored elsewhere; this is about then comparing it against data from latest head of the target branch).
It is also not related to temporal web-accessible stores for preview of documentation or code coverage. That is a separate (though also Epic) task. These have no common dependencies.
Until we have a data store to expose the generated files ( T101545: Provide infrastructure to store files by project/branch post-merge to compare with pre-merge ). There is not much we can do on this task.
I have created a root tracking task for object storage on labs: T114998. Beta-Cluster-Infrastructure needs Swift.
Has been done for the beta cluster via T64835: Setup a Swift cluster on beta-cluster to match production. Probably want to do the same for the integration labs project.
Declining given that the main motivation for this was T101544: Provide (pre-merge) code coverage reports on patchsets, which was implemented differently.