On 15-08-08 10:53 AM, Lou Burnard wrote:
On 08/08/15 18:49, Martin Holmes wrote:
On 15-08-08 10:39 AM, Martin Holmes wrote:
Yes, we could create one that you could start manually. I can give you a login for the Jinks server and permission to do that.
On the other hand, if all three of us can now build this locally, and you don't want to see fresh builds from every commit, is there a point?
No not really, tbh. Maybe we could use this as a way of encouraging more council members to figure out how to build locally? It can't be that hard....
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, or whether it's really failed; 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. But it wouldn't be hard to put together a little wiki page on how to do it. 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? Cheers, Martin