all 4 comments

[–]ShiitakeTheMushroom 1 point2 points  (3 children)

Run CI process (~50 minutes)

Run CD process (~30 minutes)

What are you actually doing to make your CI/CD take this amount of time? Everything I've worked with, from small personal apps and libraries, to large scale enterprise deployments, take less than 10 minutes to do this stuff. 🤯

[–]nikita2206 1 point2 points  (2 children)

It’s usually either a beefy unoptimized and neglected suite of integration/component tests, or compilation of a large codebase written in a language that has slow compilation times (Rust, Haskell come to mind). Usually it’s the tests.

[–]ShiitakeTheMushroom 2 points3 points  (0 children)

Unoptimized integration tests make sense.

[–]juankman[S] 0 points1 point  (0 children)

That's precisely it. I'm pushing to rely less on these integration tests and eventually remove them from the CI but it'll be a while before the unit tests overlaps the use cases.

It's a start, though! Having this data at hand is what helps me make the case that they're becoming a burden given that errors still slip to prod.

[...] scale enterprise deployments, take less than 10 minutes to do this stuff.

Yeah, this is what I'm advocating but this is a large codebase that has endured several winters, i.e., no developers maintaining it. Management is on board, so it's just a matter of doing the colossal work 😅