Begin forwarded message:
> From: Marcus Denker <[email protected]> > Subject: [Pharo-project] [Jenkins] Matrix build for tests and vm > Date: April 4, 2012 9:22:10 AM GMT+02:00 > To: Pharo Development <[email protected]> > Reply-To: [email protected] > > Hi, > > Christophe changed the Jenkins setup related to testing in a very nice way: > > -> first the current pharo 1.4 is updated to the latest. (as it used to be) > -> new: then we have a Matrix job for running tests on all plattforms. > This is one project, but it spawns test runs on all plattforms (Linux and > Mac for now). > > https://ci.lille.inria.fr/pharo/view/Build%20pipeline/job/Pharo%201.4%20Tests/ > > -> Only if this build is green, it triggers all depending builds. > > see > > https://ci.lille.inria.fr/pharo/view/Build%20pipeline/ > > > The matrix is used already for other things > -> build of Cog: > https://ci.lille.inria.fr/pharo/job/Cog-VM/ > win, linux, mac > -> Testing Cog > https://ci.lille.inria.fr/pharo/job/Cog-VM%20tests/ > (not yet windows) > > This allows us to radically simplify the Jenkins setup and trigger actions > when *all* plattforms are in a good state. > > This will allow us, for example, to automatically update the VM that is used > for running builds and tests or that is packaged in the one-click. > > TODO > -> fix 1.4 so that passing a script to the image works on Windows > -> configure to run tests on windows > -> One-Click build for 1.4 and 1.3 > -> ..... > > So we are getting somewhere! I am sure that 1.5 will be the first Pharo where > we > build *the artefact of release* completely automatically and tested from the > first > change onwards. > > And this then forms a strong basis that we can build on top. > > Marcus > > -- > Marcus Denker -- http://marcusdenker.de > >
