3 ms·
It doesn’t work well. It’s the JIRA of CI/CD: it is entrenched and does multiple things but doesn’t do any one thing well, and the people that decide what to bu
by sidlls 3y ago
It doesn’t work well. It’s the JIRA of CI/CD: it is entrenched and does multiple things but doesn’t do any one thing well, and the people that decide what to buy aren’t the people who are forced to use it so they don’t care about its quality so much
- frant-hartm 3y agoJira sucks, but I have yet to see a tracking tool which sucks less.
- lmm 3y agoJenkins is what I want to use, because for all its clunkiness it has a better deep integration with my actual build tools than any other CI tool I've ever seen. It's a pain for the admin but it's great for the user, so if anything it's the opposite of JIRA.
- ilyt 3y agoIt's not great CD bit you need entirely different system just to display code coverage in near-every other CI Near-every other CI also can't just browse which tests failed and with what message without digging directly into logs
- DirkH 3y agoGenuine question: what would you recommend instead of JIRA?