Replies: 1 comment
-
CircleCI is the bulk of our CI at this point, so I think it would be quite a lot of work to move somewhere else. I don't think we want to move back to Travis and AppVeyor is not appropriate either, so the only other option would be Github Actions. I'd rather try to deal incrementally with the changes CircleCI is throwing our way instead of throwing it our entirely. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is to ask whether we want to keep using CircleCI.
It apparently has security issues (secret rotation request) and is not exactly easy to understand with regard to concurrency (looks like we cannot run several build jobs in parallel any more):
See our apparent "Plan limit"
Also, it seems they are changing the framework such that we need to re-write some tasks anyway: From a mail received two days ago:
Beta Was this translation helpful? Give feedback.
All reactions