8 ms·
GitHub Actions and GitLab. I personally found both of those to be paradigm shifts (I went from Hudson to Jenkins to Travis CI to GitLab to GitHub Actions). Tra
by ak217 5y ago
GitHub Actions and GitLab.
I personally found both of those to be paradigm shifts (I went from Hudson to Jenkins to Travis CI to GitLab to GitHub Actions). Travis CI introduced self-serve test infrastructure configuration-as-code, GitLab introduced composability and API integration, GHA introduced many more API features (like various kinds of event sources) and better composability. Each transition also took more hosting headaches and compatibility issues off my hands.
- Fordec 5y ago+1 to this. Travis, Circle and Jenkins are entirely in the rear view in this area for me now. My only concern about Actions has become that I use it too much.
- onlyfortoday2 5y agowhy is using something too much a bad thing? LOL
- 2rsf 5y agoI have very little experience with GitHub actions but it seems much more limited and even worst it ties you to a single vendor