Why waste time with CI when you can save on thousands of dev hours by limiting yourself to only one giant fuck off release every year!
/Taps forehead so hard it causes brain damage
Comment on Who is this "Jenkins" and what now has broken him?
fkn@lemmy.world 10 months ago
I know this is a meme, but just in case someone doesn’t actually know. CI saves literally thousands upon thousands of dev hours a year, even for small teams.
devious@lemmy.world 10 months ago
Jajcus@kbin.social 10 months ago
And a lot of users' frustration, especially on more niche platforms (Linux, ARM, etc.) - things look much better on release when the code have been regularly compiled and, hopefully tested, on all platforms, not just the one the lead developer uses.
Dasnap@lemmy.world 10 months ago
It wouldn’t surprise me if this meme was made by an ops guy.
synae@lemmy.sdf.org 10 months ago
Ops loves CI systems, if the artifact doesn’t come from Jenkins (or friends) it simply doesn’t exist to us.
Dasnap@lemmy.world 10 months ago
I’m also ops and I get it, it just seems like they’re shitposting.
synae@lemmy.sdf.org 10 months ago
I sure hope so ;) else I’m on the wrong /c
engineZ@lemmy.today 10 months ago
Probably also causes lots of hours of maintenance and troubleshooting…but it’s a net gain in the end.
fkn@lemmy.world 10 months ago
I can’t even imagine not having a ci pipeline anymore. Having more than a single production architecture target complete with test sets, Security audits, linters, multiple languages, multiple hour builds per platform… hundreds to thousands of developers… It’s just not possible to even try to make software at scale without it.
astral_avocado@programming.dev 10 months ago
Multiple hour builds dear god 😵💫
Dasnap@lemmy.world 10 months ago
If you fuck up the setup and deploy to multiple environments at once with each one set to rebuild an image/program things can get long. You really have to fuck it though.
CoderKat@lemm.ee 10 months ago
As annoying as it is when someone else breaks the CI pipeline on me, it is utterly invaluable for keeping the vast majority of commits from being able to break other people (and from you breaking others). I can’t imagine not having some form of CI to preventing merging bad code.
csm10495@sh.itjust.works 10 months ago
You should have seen my last job.
rambaroo@lemmy.world 10 months ago
Hah, or my current one. Before we had CI you just directly committed to master (on SVN). It was incredible how unstable our build was. It broke basically everyday. Then one of the senior back end guys got promoted to architect and revamped the whole thing. Probably saved the company tens of millions dollars in man hours, at the very least.
Eufalconimorph@discuss.tchncs.de 10 months ago
Even better is when you restrict merges to trunk/main/master/develop (or whatever you call it) to only happen from the CI bot *after all tests (including builds for all supported platforms) pass. Nobody else breaks the CI pipiline, because breaking changes just don’t merge. The CI pipeline can test itself!
TheBananaKing@lemmy.world 10 months ago
I often wonder if there isn’t some goodharty kind of local-maximum trap hiding in this…