3 ms·

I feel for all the engineers impacted by this layoff, but I do not agree that they are "the best CI/CD platform on the market". Our small team has moved away f

by aftbit 4y ago

I feel for all the engineers impacted by this layoff, but I do not agree that they are "the best CI/CD platform on the market". Our small team has moved away from CircleCI for all new projects. We are mostly using Github Actions these days. The major driver was not cost, which was minimal for our team, but the fact that CircleCI keeps breaking our build. In the ~5 years that we have used them, we have experienced at least 3 major breakages, including the migration from v1 to v2 yaml configs and the new docker architecture. They have strayed far from their early value prop and cause us more headaches than delight. CircleCI, if you are listening, all I want with CI/CD is to forget about it, not have to revisit a working project every year to rearchitect it onto a new builder.

hoherd 4y ago
I guess this is a good place to remind folks that scheduled workflows will probably stop working soon > The scheduled workflows feature is set to be deprecated. Using scheduled pipelines rather than scheduled workflows offers several benefits. Visit the scheduled pipelines migration guide to find out how to migrate existing scheduled workflows to scheduled pipelines. https://circleci.com/docs/configuration-reference/#schedule https://circleci.com/docs/configuration-reference/#schedule One more thing to migrate out of the config file in the repo and off behind some API call or pointy-clicky UX. Edit: it looks like they've postponed the deprecation, which was originally planned for 2022-06-03 https://discuss.circleci.com/t/scheduled-pipelines-are-here/41684 https://discuss.circleci.com/t/scheduled-pipelines-are-here/...
parkerhiggins 4y ago
Also moved off CircleCI to GitHub Actions for similar reasons.
aeyes 4y ago
It is going to be interesting to see how many breaking changes GitHub Actions will have in the next 5 years. At least they have the advantage that they weren't a first mover so they hopefully learned from the mistakes of other companies.
SkyPuncher 4y ago
> including the migration from v1 to v2 yaml configs Holy shit. I forgot about this. I was infuriated when I needed to waste nearly a week rewriting my config with more complexity and reduced features. I literally wasted a week of my life so a company I was paying could save costs. I would have happily paid 50% more to not have to waste my time on that crap.
stairlane 4y ago
We also made the same switch for the same reasons. Outages were so common this past year (particularly on Wednesdays for some reason), that it's become a meme of being an indicator for if it's Wednesday at our company or not.
nfx_dev 4y ago
Honestly, we have run into similar issues with GHA as well. I recently heard about Drone/Harness CI. I tried it last week and it is holy shit fast. Not sure how they do they do it without charging an arm and a leg. We are probably going to go with Harness. They are the only other platform other than Gitlab and GHA. Some competition is good.

by aftbit 4y ago

hoherd 4y ago

I guess this is a good place to remind folks that scheduled workflows will probably stop working soon > The scheduled workflows feature is set to be deprecated. Using scheduled pipelines rather than scheduled workflows offers several benefits. Visit the scheduled pipelines migration guide to find out how to migrate existing scheduled workflows to scheduled pipelines. https://circleci.com/docs/configuration-reference/#schedule https://circleci.com/docs/configuration-reference/#schedule One more thing to migrate out of the config file in the repo and off behind some API call or pointy-clicky UX. Edit: it looks like they've postponed the deprecation, which was originally planned for 2022-06-03 https://discuss.circleci.com/t/scheduled-pipelines-are-here/41684 https://discuss.circleci.com/t/scheduled-pipelines-are-here/...

parkerhiggins 4y ago

Also moved off CircleCI to GitHub Actions for similar reasons.

aeyes 4y ago

It is going to be interesting to see how many breaking changes GitHub Actions will have in the next 5 years. At least they have the advantage that they weren't a first mover so they hopefully learned from the mistakes of other companies.

SkyPuncher 4y ago

> including the migration from v1 to v2 yaml configs Holy shit. I forgot about this. I was infuriated when I needed to waste nearly a week rewriting my config with more complexity and reduced features. I literally wasted a week of my life so a company I was paying could save costs. I would have happily paid 50% more to not have to waste my time on that crap.

stairlane 4y ago

We also made the same switch for the same reasons. Outages were so common this past year (particularly on Wednesdays for some reason), that it's become a meme of being an indicator for if it's Wednesday at our company or not.

nfx_dev 4y ago

Honestly, we have run into similar issues with GHA as well. I recently heard about Drone/Harness CI. I tried it last week and it is holy shit fast. Not sure how they do they do it without charging an arm and a leg. We are probably going to go with Harness. They are the only other platform other than Gitlab and GHA. Some competition is good.