3 ms·
The biggest issue is that I've experienced some of that creep with GitHub Actions. It's a mess, doesn't do what it needs to do and besides "presenting" features
by oneplane 5y ago
The biggest issue is that I've experienced some of that creep with GitHub Actions. It's a mess, doesn't do what it needs to do and besides "presenting" features/functionality it can't actually do even the basic things a nasty old Jenkins installation in an AWS ASG does.
They practically just copied some Azure CI stuff over (which was obviously written from a completely different perspective/mindset) using a tech stack that is old yet immature when compared to even relatively young products like GitLab CI.
If a company wants to come up with a CI product but can't even get on par with basic nominal GitLab CI features and usability, what's the point...
- unemphysbro 5y agoeven from a documentation perspective, GitLab CI is so much easier to digest then azure pipeline docs.
- FridgeSeal 5y agoAzure pipelines is the most verbose and confusing CI tool I’ve had the misfortune of using. Why does it require so many steps? Why are they so verbose? It feels like writing glorified bash scripts (in which case why am I using a CI tool?) but worse.
- wussboy 5y ago“Old, yet immature”. Perfect description.