make a dashboard page

[lsf37]

We should have an overview page somewhere with the CI status of all relevant repos.

This could be a markdown file in a repo somewhere, or a web page on sel4.systems.

Ideally generated automatically from repo content, so that we don't have to update manually if a test is added/removed.

[axel-h]

Do you know if github supports this already somehow form the builds running on PRs? What is the plan about bamboo, will it come back and then may have a read-only public page?

[lsf37]

Need to check, but I doubt GitHub has something that is cross-repo.

Bamboo will be retired, the license was for CSIRO and is not being transferred.

[lsf37]

Need to check, but I doubt GitHub has something that is cross-repo.

Medium-quick google check on this doesn't turn up anything. You can of course see the overall status of all checks on a single repo at the tick/cross at the most recent commit, and you can put in a status badge for any checks that run as github actions, but I haven't found anything that shows status of multiple repos.

[lsf37]

I was thinking something like below. Needs a bit more work on ordering so that there is not that much need for scrolling, but the information itself is there:

seL4 CI status

• cakeml_libs:

  

• camkes:

  

• camkes-manifest:

  

• camkes-tool:

  

• camkes-vm:

  

• camkes-vm-examples:

  

• camkes-vm-examples-manifest:

  

• camkes-vm-images:

  

• camkes-vm-linux:

  

• capdl:

  

• ci-actions:

  

• docs:

  

• gh-testboard:

  

• global-components:

  

• graph-refine:

  

• l4v:

  

• mcs-examples:

  

• mcs-examples-manifest:

  

• musllibc:

• projects_libs:

  

• pruner:

  

• refos:

  

• refos-manifest:

  

• rumprun-sel4-demoapps:

  

• seL4:

  

• seL4-CAmkES-L4v-dockerfiles:

  

• sel4-tutorials:

  

• sel4-tutorials-manifest:

  

• sel4bench:

  

• sel4bench-manifest:

  

• sel4runtime:

  

• sel4test:

  

• sel4test-manifest:

  

• sel4webserver:

• sel4webserver-manifest:

  

• seL4_libs:

  

• seL4_projects_libs:

  

• seL4_tools:

  

• util_libs:

  

• verification-manifest:

  

• website:

  

• whitepaper:

  

[lsf37]

Will have a look at cleaning this up and adding it to the docs site. (Easier to edit than the main website and more targeted at developers).

Any comments/concerns before I go ahead with that?

[kent-mcleod]

I think if you are adding to the doc site then it should end up in two places:

• A single page that has all of the statuses. This could be its own page or part of https://docs.sel4.systems/projects/
• A stub on the project sidebar that shows for a specific project if in that project's tree on the docsite. The docsite has per project yaml files which you could use to make it easier to keep tests in sync: https://github.com/seL4/docs/tree/master/_data/projects

[lsf37]

Part one of this is now online at https://docs.sel4.systems/processes/test-status.html

I have not looked at the sidebar idea in detail yet. It sounds feasible, but would be more manual, I think. At least I don't think it'd be easy to generate the necessary changes to the project yaml files. Then again, those files probably just need the list of tests, and the rest can be done in the website build itself.

[lsf37]

One additional thing I just noticed looking through that page: after a certain time of inactivity, GitHub seems to be removing not only the logs but all traces of earlier action runs. In particular ref-os and mcs-examples have not had any activity for over a year, which means the badge links do not work any more.