-
Notifications
You must be signed in to change notification settings - Fork 129
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
Create nightly CI process that tests against CLN master, use CLN latest release binary for "on push" diff CI testing #407
Comments
This seems better, yeah :) |
Do we still want to test master nightly to alert us of upcoming breakages? I liked your idea of doing a "diff CI" for pushes, and a "full CI" nightly. |
We want two different test processes:
Side note: If stuff breaks on master, we have time to notify plugin maintainers that their plugins are broken and they need to fix before the upcoming CLN release. Once the new release is out, if plugins still aren't fixed, we move them to archive. |
We also want to move to a system where all plugins are built from source every night, and we also want to enforce that all plugins have tests, ideally useful tests. But this can be a separate issue. |
I don't know how to get @fmhoeger to appear in the list of assignees, so i'm assigning myself. |
Would it make sense to modify above line to read:
|
Sure, that sounds good. |
We want to test against a recent version to get tipped off when deprecations hit us, but the release is new enough, no need to waste CI cycles rebuilding CLN
master
over and over again.The above snippet will get us the latest download URL for Ubuntu 22.04.
The text was updated successfully, but these errors were encountered: