Use Gitlab Pages for providing development builds
Background
Maintaining the lists of development builds for Firefox and Chrome is currently done by distcontinued (see #212 (closed)), instead we want to maintain a list of (unsigned and archived) extension packages on the Gitlab Pages.createNightlies.py
from abpssembly
, involving multiple distribution techniques across 6 hosts in total. Since we already have a newer (not used until !8 (closed) is landed) mechanism to maintain a list of recent development builds for Firefox
What to change
- Let the jobs
download:release
anddownload:devbuild
also maintain and consider abuild_list.json
file, which should be updated with new builds. - When a build is already listed in
build_list.json
, don't proceed with downloading the package. - Make sure that the
build_list.json
is consistently available in every pipeline / job (so far only scheduled pipelines formaster
). - Let the files listed in
build_list.json
be grouped by commit. - Let the
build_list.json
contain relevant information about the contained builds:- Commit it was build from
- Creation time
- Download URL (from a Job's artifacts)
- Version number
- Target platform
- File size
- Release channel (e.g.
Release
andPre-Release
)
- Keep up to 150 distinct groups ( = commits) in the file.
- Whenever the file is update, render a representative HTML page from it's content and publish that to the
GitLab Pages
.
Additional tasks:
-
Preseed a build_list.json
file with a list of recent development and (if applicable) release builds for Chrome and Firefox (done by temporarily pushing a feature branch, which triggers a downstream pipeline in triluc/abpchrome_buildlist_generator and publishes a fresh distribution listing).
Edited by Tristan Lucas