[benjaminwootton]

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]

GH Actions is just CI, maybe crude CD, and not the best at that.

It and (GitLab CI) ate Jenkins

[lmm]

Jenkins 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]

What does Jenkins do that you can't do with GH Actions and Flux?

[lmm]

Based 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]

I have been away from Jenkins for a while, that all sounds like stuff I never used, (thanks!)