3 ms·
GitHub actions must have eaten most of the DevOps tooling market. It’s pretty good and it’s fine for the vast majority of pipelines.
by benjaminwootton 3y ago
GitHub actions must have eaten most of the DevOps tooling market. It’s pretty good and it’s fine for the vast majority of pipelines.
- Yasuraka 3y agoGH Actions is just CI, maybe crude CD, and not the best at that. It and (GitLab CI) ate Jenkins
- lmm 3y agoJenkins still does stuff that you can't do with GH Actions. Actions ate Travis / TeamCity / CircleCI, all the "more polished Jenkins for the 80% use case" products.
- yebyen 3y agoWhat does Jenkins do that you can't do with GH Actions and Flux?
- lmm 3y agoBased on the last time I looked: good handling of dependencies between builds (e.g. the ability to do an "edge build" where for any change in a given project, you check whether that will break your other projects when they upgrade to depend on that), advanced scheduling, plugins that integrate all sorts of random tools into your build views.
- yebyen 3y agoI have been away from Jenkins for a while, that all sounds like stuff I never used, (thanks!)