[tei-council] ongoing working with Jenkins

[Sebastian Rahtz]

It may be helpful to look at http://bits.nsms.ox.ac.uk:8080/jenkins/
and consider how this continuous integration works now.

Look at the times for P5 Test, P5 Documentation, and P5. The idea
is that each change which is committed is first tested for
schema-related problems  (3 min 47 seconds); if no problems
are found there, documentation is built (4 min 57 seconds);
if that is all OK, the main distribution is built _from scratch_. This does do a few
extra things which can fail (building Exemplars) but mainly consists
of clean builds in all the right forms (ie all the languages for web
pages, Debian packages and ones for Sourceforge, making
mechanical schema conversions), and takes an extra hour.

The vast majority of mistakes are therefore caught in the first 3-4
minutes, but to be sure you need to wait just over an hour.

I am not saying this is perfect, or even right yet, but does the idea
seem OK?

it of course does not preclude work to make any particular stage
go faster.
--
Sebastian Rahtz      
Director (Research Support) of Academic IT Services 
University of Oxford IT Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431