Skip to content
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

Add a nightly CI run #734

Merged
merged 1 commit into from
Mar 29, 2024
Merged

Add a nightly CI run #734

merged 1 commit into from
Mar 29, 2024

Conversation

cameel
Copy link
Member

@cameel cameel commented Mar 15, 2024

We should really have a nightly run in this repo because there's not that much traffic here and we sometimes miss CI being broken. With a nightly run we won't have to remember to run CI manually and we'll actually notice breakage as it happens, not just before a release.

It would be useful to also have notifications for the Matrix CI channel. And a run with a nightly binary from solc-bin, which would have detected breakage like #732 and, combined with that notification, would let us know when nightlies in solc-bin are broken (ethereum/solidity#13507). I did not do any of those things though. This is just a simple nightly workflow build quickly out of what I already had at hand.

@cameel cameel self-assigned this Mar 15, 2024
@cameel cameel merged commit d61cd57 into master Mar 29, 2024
16 checks passed
@cameel cameel deleted the nightly-ci-run branch March 29, 2024 18:42
@cameel
Copy link
Member Author

cameel commented Mar 29, 2024

Not sure what's up with the required coveralls job here. It randomly changed name (again) so Github started assuming that the job did not run. And the PR does not even touch anything related to it. On top of that Github did not let me change the requirement to the new name so I thought I'd just remove it and readd after merging, but now the job completely disappeared from settings...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants