Hi Lou, On 15-08-08 01:39 PM, Lou Burnard wrote:
On 08/08/15 21:10, Martin Holmes wrote:
I'm not sure what the value of that is, actually. The idea of Jenkins is that it provides a known, robust build environment. If you build locally and it fails, you have no idea whether it failed because your build environment is screwed up somehow,
almost never happens in my experience: if it fails it's cos you changed something, and you know what you have changed.
or whether it's really failed;
"really" failed? as opposed to?
Failed because you have an old Saxon on your system, or because you accidentally deleted a file, or pointed at the wrong stylesheets, or called make targets in the wrong order, or the mrs joyful prize for rafia work toppled off the shelf onto your keyboard at the wrong moment.
and if it succeeds, you also don't know whether it succeeded because you have a local copy of a file that is missing from the repo, and when you commit it will fail anyway on Jinks.
that's a very specific problem, though admittedly quite a common one: jinks is VERY useful as a way of catching it though.
But it wouldn't be hard to put together a little wiki page on how to do it.
I think I started to do that once... will look.
If you find it, let me know. I'll contribute. The key thing is pointing at a local copy of the Stylesheets.
Do we suggest that you must build your own rnv, or that you must install the TEI packages to get it? What if you're on a Mac -- does it come with rnv?
Or shall we just abandon using rnv?
Hmm. I don't really like the notion of abandoning checks. Isn't RNV the only thing that's checking our .rnc products? Cheers, Martin