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

Move CircleCI to GitHub Actions #4373

Open
fendor opened this issue Aug 3, 2024 · 1 comment
Open

Move CircleCI to GitHub Actions #4373

fendor opened this issue Aug 3, 2024 · 1 comment
Assignees
Labels
CI Continuous integration type: enhancement New feature or request

Comments

@fendor
Copy link
Collaborator

fendor commented Aug 3, 2024

CircleCI has been tagging along for quite some time now. But it did cause a couple of issues, for example in #4282.

There is no apparent reason why we might want to have a separate CI for stack and cabal, so we should unify the CI and use only GitHub action.

A potential disadvantage is that the additional stack jobs might overspill our CI cache limit.

The cache sizein CircleCI is currently:

Found a cache from build 67987 at v4-stack-cache-arch1-linux-amd64-6_85-stackage-nightly-9H4jA_vWfu4DX2U+oJlCNgYnwmWpFeeSs1ich4bwKTc=
Size: 686 MiB
Cached paths:
  * /root/.stack

and

Found a cache from build 67986 at v4-stack-cache-arch1-linux-amd64-6_85-stackage-lts22-uMKE535wPCuBR3jwBD8F3A7WLxI4RRRP_JyQHhniH1w=
Size: 675 MiB
Cached paths:
* /root/.stack

That's definitely too much for our 10GB limit.

@fendor fendor added type: enhancement New feature or request CI Continuous integration labels Aug 3, 2024
@fendor fendor self-assigned this Aug 3, 2024
@michaelpj
Copy link
Collaborator

I thought we had an issue for this, and indeed there is #3086... which apparently I closed myself by mistake 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous integration type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants