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
Update CI tooling for raku/doc #4195
Comments
My cleanup has probably broken the existing CI we had for tests @dontlaugh, any recommendations for how we should be running our CI tests? We need:
In my opinion, we're fine running tests ONLY on the files that changed for the given commit, but if we do that, we need to definitely monitor when they failed and make them green when they're clear. This makes it more complicated than just running all tests for everything and then we can ignore all previous failures when we get any 100% pass. |
I have some infra work to do to facilitate this. Here is the architecture I'm going to pursue (it's what I've implemented for $DAYJOB, as well as for my personal servers). Compute Substrate
The current CI setup for Raku/doc-website is effectively doing all this already, but I need to migrate that stuff into the shared Hetzner account where we are now running docs.raku.org Config BackupThe Packer files will be checked into Raku/infra; container builds (in this case, LXD containers) are not exactly idempotent (since running Our current CI for Raku/doc-website already uses this architecture. I just need to re-implement it in the common Hetzner account. |
Hi ! After a short talk with @coke creating this suggestion ticket.
https://irclogs.raku.org/raku/2023-02-08.html#01:31-0001
The text was updated successfully, but these errors were encountered: