Remis Baima 10 Years Ago AFAIK the "normal" CI process works the way that you describe (and also has the issues that you describe :-). But I have a question (which I hope that makes sense): why not simply create a "pre" master branch where all check-ins will be done, and this "pre" master branch will be automagically synced with the "real" master branch *only* when the build is green?So, all developers would only checkout clean code from the "real" master branch and would never be able to check-in dirty code into the "real" master branch. This way you would avoid many of the issues that you describe. Please sign in to reply. Reply as... Cancel Manuel de la Peña Remis Baima 10 Years Ago Hi Remis, thanks for your comment!Unfortunately our scenario is more complex as we have different production versions to support. Not to mention that we have several products now which needs to be compatible with different versions of each other. So having a pre master branch for each version could be hell for us at this moment But we are trying to do our best to improve that.Cheers! Please sign in to reply. Reply as... Cancel
Manuel de la Peña Remis Baima 10 Years Ago Hi Remis, thanks for your comment!Unfortunately our scenario is more complex as we have different production versions to support. Not to mention that we have several products now which needs to be compatible with different versions of each other. So having a pre master branch for each version could be hell for us at this moment But we are trying to do our best to improve that.Cheers! Please sign in to reply. Reply as... Cancel
Will Morton 10 Years Ago Absolutely! We called him the 'Build Barbarian' (he had a little hat with horns), but the same function.A corollary to this rule is not to commit your stuff to master/trunk if you're going to go home before you see the build of your change go green! If you have to go now, commit your stuff to a branch, then on Monday morning merge it to master and watch it go Please sign in to reply. Reply as... Cancel