Re:Patterns for Managing Source Code Branches
by hinkley on Monday April 20, 2020 @08:51PM
(#22930665)
I don’t think it occurred to me that one day I would have to choose between CI and code reviews, and yet that’s where I’ve been living for years.
I think I’d rather have CI.
Re:Patterns for Managing Source Code Branches
by NomDePlum on Monday April 20, 2020 @10:45PM
(#22931314)
Nothing to stop code reviews either. Just don't make them a gateway. Allow code to be merged then reviewed if necessary. If you have good common coding practices and testing then likely more than safe.
Re:Patterns for Managing Source Code Branches
by corpMaverick on Wednesday April 22, 2020 @11:59AM
(#22946961)
Great advice. This is why it is good to go back to the basics. Adding gateways goes against any lean principles, introduces delays (=waist) in the process.
As far as I remember, Continuous Integration (CI) was about merging your code with the rest of the team as frequently as possible. Jenkins, and other tools were not even in the horizon. Because in the waterfall prehistory, some teams used to divide the system in parts and integrate the source code at the end. And it was hell. So now we have these powerful tools like git, and in a way we use them to cheat and not do CI.