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?
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.
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?