wilfwilson
commented
2 years ago This is a work-in-progress. In particular, most of the repositories in the gap-infra organisation (i.e. the ones that are now archived any private) have now been combined into this new integration repository (I'd be happy to change the name is someone has a better suggestion).
Some of the information here is out of date, so it would probably be best to close this issue and put any remaining points into their own issues.
fingolfin
We could consolidate all those repositories into a single repository (or perhaps two: one for pkg-tests, one for GAP tests), with branches for each of the different test variants. So there would branches with names like these:
pkg-tests-master-staging(orpkg-tests-master-failing?)pkg-tests-master-passingor...-working(I'd prefer to have an explicit suffix)pkg-tests-master-develpkg-tests-stable-4.11-stagingpkg-tests-stable-4.11-passingpkg-tests-stable-4.11-develgap-tests-mastergap-tests-stable-4.11Suppose we put these all into a repository
travis-tests(or perhaps there'd be two repositories: one for the package tests, one for the GAP testsuite, whatever, that's a minor detail).Then one could see the status of each branch / test variant on the Travis website with one glance on a page similar to this one https://travis-ci.org/gap-system/gap/branches.
That repository could also have a
gh-pagesbranch showing information similar to what https://github.com/gap-system/gap-distribution shows right now. Or itsmasterbranch could have a README.md with those badges. Or both, or whatever. It would be a natural place for this kind of information.