[tei-council] build failure

[Martin Holmes]

Hi Syd,

On 13-12-12 07:04 PM, Syd Bauman wrote:
> I just checked-in changes to Stylesheets (in gitHub) and to P5. The
> latter failed to build on Jenkins, I think because it is not using the
> changes of the former. The former failed to build on Jenkins, and I
> have no idea why. (It fails to validate test.epub, which has nothing
> to do with the change I made, which was to extract-isosch.xsl.) Nor do
> I understand why the TEI build was attempted (or maybe just finished?)
> before the Stylesheet build, when I pushed the Stylesheet changes ~5
> mins before I committed the P5 changes.

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.

> I also can't get P5 to build on my Ubuntu desktop; but it does build
> on my Mac laptop. This is weird, because it dies on trying to generate
> PDF with xetex, which is installed in Ubuntu but (as far as I
> remember) not on my Mac. This is frustrating, because I don't care
> about the PDF version, I just want to check for errors and have an
> HTML version of the Guidelines. I've spent > 3 times as much time
> trying to get P5 to build than I have making the changes to
> extract-isosch.xsl and validators.xsl.

I don't think there's any advantage in trying to build anything locally, 
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.

Cheers,
Martin