[tei-council] Jenkins config changes

[Martin Holmes]

Stylesheets seems to have failed because it's using old artifacts from 
prior to the 2.2.0 release (I see a mismatch between a line of text I 
changed in a typo fix after release time).

I'm going to kick off P5-Test instead, and see if that goes OK. If the 
P5s work, I'll wipe the Stylesheets workspace and start that one again. 
Then they'll all go through one more time.

I have a thought: we should make the occasional version change purely 
for internal testing, between releases. If we once in a while did e.g. 
2.2.1, 2.2.2 etc., but just for Jinks and not for release, we'd be able 
to inspect the results at our leisure, and know if the real release 
process would be likely to experience problems.

We could have a numbering convention to indicate a "not for release" 
version.

Cheers,
Martin

On 12-10-27 11:22 AM, Sebastian Rahtz wrote:
>
> On 27 Oct 2012, at 19:19, Martin Holmes <mholmes at uvic.ca>
>   wrote:
>
>> the problem with the old version and date has cleared. I think Sebastian
>> wiped his workspaces, forcing the job to build everything afresh, which
>> was needed to get clean files for deployment, but my server is still
>> unclean; that means if it builds good output, the problem shouldn't
>> recur next time we change the version number, but if it doesn't, then it
>> will, if you see what I mean.
>
>
>
> the cleanliness should be achieved by each task in Jenkins now starting
> with a "make clean"
> --
> Sebastian Rahtz
> Director (Research Support) of Academic IT Services
> University of Oxford IT Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>