[MDBF-473] Centralize Ecosystem CI results somewhere (or be alerted of failures) Created: 2022-09-19 Updated: 2022-11-08 |
|
| Status: | Open |
| Project: | MariaDB Foundation Development |
| Component/s: | Buildbot |
| Affects Version/s: | N/A |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor |
| Reporter: | Faustin Lammler | Assignee: | Faustin Lammler |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
As discussed with danblack, one of the Ecosystem CI strategy is to ask directly upstream to test against MariaDB. See: https://github.com/grooverdan/wordpress-develop/commit/8a2079fa2bc3f9ea27a0d1016d5c8f9a2e1c6369 The purpose of this MDBF is to find a solution to be alerted if Upstream Ecosystem CI have failure. First suggestion/idea: |
| Comments |
| Comment by Daniel Black [ 2022-09-20 ] |
|
Even a github markup page like mariadb-docker-library (all the shields at the bottom). The shields.io has a good collection of URLs that can be used against multiple types of CI /test systems. |
| Comment by Faustin Lammler [ 2022-11-07 ] |
|
danblack here is an example that can probably inspire us https://ansible.jeffgeerling.com/ |
| Comment by Daniel Black [ 2022-11-08 ] |
|
Nice! Given this is all static I assume a GH page is all that's required? |
| Comment by Faustin Lammler [ 2022-11-08 ] |
|
Yep, we could probably create a markdown file on https://github.com/MariaDB/buildbot and then decide where to include it (maybe not difficult to import/iframe it on BB)... |