Re:Jenkins Is Getting Old
by FrenchyJiby on Monday April 29, 2019 @03:47PM
(#19781934)
Internal libraries and similar fun stuff. Common build step ~~ same packager commands run on them.
Management is fairly simple with a template + seed jobs. It's just ... everything else is annoying.
I don't understand what you mean by one team per repo?
I agree, as I keep saying at $WORK: Jenkins is the least-worst system out there.
How many teams do you have? In all seriousness, if you aren't talking at least one team per repo, have you considered a monorepo setup? Aren't you burning time managing those many similar repos with many similar build steps?
That said, even in a monorepo, I still prefer Jenkins compared to cleaner seeming cloud offerings due to its limitless flexibility.