Stef, Naive question: could you simply let Jenkins do the testing, and investigate/roll-back if it reports problems? If Jenkins can reliably, based on unit tests, report a last successful build, you might be at a good place. In that world, you would integrate and let Jenkins tell you if it was a bad thing to do. Like I said, it might be naive.
Bill ________________________________________ From: pharo-project-boun...@lists.gforge.inria.fr [pharo-project-boun...@lists.gforge.inria.fr] on behalf of Stéphane Ducasse [stephane.duca...@inria.fr] Sent: Saturday, March 24, 2012 10:37 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] 1.4 is now green... >> >> >>> .. 1.4 has now all tests green on jenkins (Mac and Linux). >>> >>> The nice side-effect is that all the jobs that check VM builds are now >>> green, too. >>> >>> https://ci.lille.inria.fr/pharo/view/Pharo%201.4/ >>> >>> The idea is to now to just never ever integrate anything that makes a test >>> break... >> >> ok but it means that we should run 20 min tests each we integrate >> something…. how boring. >> We can try. >> >> Stef > > That's why you should use a full automatized process .... :whistle: ^^ indeed. I want :) Stef
