-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Make a "Nightly build" #1678
Labels
Comments
@feross I think this is a great idea! It would certainly help users test things and ultimately would help squash certain bugs like the CPU over-utilization problem. |
Is there a checklist to set this up? Anything we can do to help? :) |
This would be great! With the improved GitHub actions features now, this can be easily implemented ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm back from my open source break now and happy to continue doing releases of WebTorrent Desktop manually as we determine that new releases should go out. It's best to not share the signing keys – the fewer folks who have them, the less that can go wrong. At the moment, the only other person with the keys is @dcposch since he helped build the first version of WebTorrent Desktop with me and did many of the releases. (In a year, the keys will expire and when I renew them, I'll be the only person with current signing keys.)
I'd like to work toward fully automating the packaging and release process so no one needs have the keys locally. It's almost fully automated, but there are still a few manual steps. If we fix these up, then we can use GitHub Actions to automatically produce signed nightly builds (assuming the keys can be securely stored in environment variables on GitHub).
It would be super cool if anyone could download a "nightly" version of WebTorrent Desktop with the code from
master
.The text was updated successfully, but these errors were encountered: