Use more structured reports
Rather than using plaintext error messages, use readable codes and
structured metadata for errors and updates to make them easier
to process.
This will be particularly useful for filtering: for instance we
preserve the branch information rather than muddling it in the
error message.
Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
parent
d16a3adf
No related branches found
No related tags found
Showing
- .gitlab-ci.yml 2 additions, 0 deletions.gitlab-ci.yml
- bin/classes.py 34 additions, 0 deletionsbin/classes.py
- bin/dashboard 12 additions, 2 deletionsbin/dashboard
- bin/packaging-check-invariants 165 additions, 72 deletionsbin/packaging-check-invariants
- bin/packaging-updates 5 additions, 2 deletionsbin/packaging-updates
- bin/packaging-updates-upstream-linux 32 additions, 19 deletionsbin/packaging-updates-upstream-linux
- templates/index.html.jinja2 179 additions, 37 deletionstemplates/index.html.jinja2
This diff is collapsed.
-
mentioned in commit c6e8b1f3
-
mentioned in merge request !222 (merged)
-
mentioned in commit 1320d4a3
-
mentioned in commit 39209d78
-
mentioned in commit d332515d
Please register or sign in to comment