Abderrahim Kitouni created an issue:
Now that flat-manager is working, we would like to use it for nightly apps too. Here is a rough plan of the tasks needed to do it. I marked every task with whoever I think can do it best, but I can help with everything that doesn't require special permissions.
But before, I have a couple of questions:
- Is it okay to use a single repo instead of gnome-nightly/gnome-apps-nightly split?
- Is it okay to have a completely new name, say nightly.gnome.org/repo and mark older repos as EOL and ask people to migrate?
- Am I correct in thinking that both our arm runners are in fact aarch64, and can run both 32bit and 64bit code?
Here is my plan:
- Provide an arm shared runner
- tag armv7 (a.k.a 26651128, a.k.a https://gitlab.gnome.org/GNOME/gnome-build-meta/runners/72) to run aarch64 jobs as well. (@akitouni)
- make packet-1-c1-large-arm (a.k.a. eadc863c, a.k.a. https://gitlab.gnome.org/GNOME/gnome-build-meta/runners/20) a shared runner (@barthalion / @jjardon)
- Provide images for building flatpaks in gitlab CI
- aarch64 versions of gnome-runtime-images (@alatiera / @akitouni)
- Decide what to do for arm and i386 (in the same image as 64bit or separate images)
- Migrate a test app to flat-manager
- maybe epiphany? (@mcatanzaro / @akitouni / @alatiera)
- Update CI Templates as needed? (@alatiera / @akitouni)
- Improve the experience downloading from the new server
- Enable HTTP/2 (or at least connection keep-alive) on gbm-builder. (@barthalion / @averi)
- Announce it publicly
- Decide on a final name for the repo
- Decide on a deprecation period for the old repos
- Announce the migration
- Mark the old repos as EOL
- Decomission old stuff (after the deprecation period is over)
- Decommission sdkbuilder.g.o (@averi)
- make gnome{1,2}.codethink.co.uk gitlab CI runners (@jjardon / @barthalion)
- drop the old repos from spinner.g.o and add redirects if we decide not to break compatibility.
/cc @alexl @aklapper @ebassi @matthiasc @tvb for comments.