3 ms·
Continuous Integration tools. I started with Jenkins and hated it, because it really encouraged configuration through an awful web interface. CI configs should
by simonw 6y ago
Continuous Integration tools.
I started with Jenkins and hated it, because it really encouraged configuration through an awful web interface. CI configs should live in version control!
(I know you can do that with Jenkins these days but I still haven't figured out how myself).
Then I got going with Travis CI and loved it - then Circle CI, then GitLab CI and today I'm mostly using GitHub Actions.
Every single personal project I build uses CI now. My tests, packaging and deploys are all automated from day one. It's an enormous productivity boost and lets me manage way more projects without worrying that I'll forget how to test them / package them / deploy them.