[tei-council] build failure

[Syd Bauman]

Thanks, Martin.


> P5-Test would start to build as soon as it noticed the change to the
> P5 source on SVN; it checks every five minutes. It probably noticed
> that before the Stylesheets build had completed, so it used the old
> stylesheets build output. Once you get the Stylesheets build to
> complete successfully, it should kick off the procession of P5 builds
> automatically.

Check, thanks. 


> I don't think there's any advantage in trying to build anything
> locally, 

I think there is a very fundamental advantage to being able to build
locally. Perhaps I'm being old-fashioned, but I still believe in the
idea that the earlier in your work-flow you catch an error, the less
that error costs you. Whether the incremental extra cost to catch the
error earlier is more savings than the gain of catching it earlier
(i.e., whether it's worth the effort) may be debatable, but in a case
like ours, where we expect the earlier checks to (over time) catch
*lots* of errors, I expect it is well worth it. That said ...


> but there is an Ubuntu script that will set your machine up as a
> Jenkins build server:
>   <http://wiki.tei-c.org/index.php/Setting_up_a_Jenkins_server>
> You could set up the Jinks server on your machine, then just run it
> and tell it to build whenever you need it.

... this may be a whole lot better way to catch those errors earlier.
Thanks! :-)