-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare CI workflow for nightly releases #1555
Conversation
|
Here is the built release: https://github.com/rust-lang/rustc-perf/releases/tag/nightly. |
|
Rebased over |
|
I'd like to merge this before #1565 so that we can provide a nightly release for users that do not want to download Ping @Mark-Simulacrum |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems okay for now. Let's see how it works out in practice, we may want to put the site binary into our perf S3 bucket as an alternative to GHA if there's any problems with the overwriting here.
|
I use a similar approach in a different repo and it works fine I think. The only issue is that the overwritten nightly release still keeps the "publication date" of the first release (so it looks like the release was published a long time ago), but that's just a cosmetic GitHub UI thing, the textual description of the release clearly states the date of the nightly. |
This new CI workflow builds a
rustc-perfsite binary each day (night) and publishes it into a draft GH release. The release is overwritten each day, so we won't be spammed with hundreds of releases.