diff options
| author | Mukilan Thiyagarajan <me@mukilan.in> | 2023-04-09 10:14:45 +0530 |
|---|---|---|
| committer | Mukilan Thiyagarajan <me@mukilan.in> | 2023-04-12 21:02:07 +0530 |
| commit | f1ba708cf77f7ee7dd7c718f48c4f0532bba1845 (patch) | |
| tree | c92c0431aebbc947e487d702e0b973e2d87101f8 /python/tidy | |
| parent | 1f3837dd43b9c10f083dc401f0901a6a900ba2cb (diff) | |
| download | servo-f1ba708cf77f7ee7dd7c718f48c4f0532bba1845.tar.gz servo-f1ba708cf77f7ee7dd7c718f48c4f0532bba1845.zip | |
Upload nightly builds to Github Releases
This change extends the `mach upload-nightly` command to
publish the nightly builds for all platforms as GH Release
assets.
The GH releases are made on a separate repository so
that we can persist older nightly builds without having
to accumulate git tags for them.
Some design tradeoffs in this approach are:
1. To allow the 'latest' link from servo.org to remain stable,
the release assets are named 'servo-latest.{ext}' instead of
containing the release tag/date.
2. The release is created as draft and published atomically
when all platforms have been built successfully. This allows
us to link to the 'latest' alias from servo.org while
gauranteeing that it contains builds for all platforms.
The other option here would be to have code in servo.org UI
that uses GH API to find the most recent release with a
successful build for a given platform.
3. The tags in the nightly repo are all based on the same
commit that has no relation to servo code base.
Signed-off-by: Mukilan Thiyagarajan <me@mukilan.in>
Diffstat (limited to 'python/tidy')
0 files changed, 0 insertions, 0 deletions