Re: [tei-council] Jenkins build process

I only see one objection in there, but I think it's sufficient: if it's someone else's program, that's not where we should be mucking.

I've got two objections to trying this (well, maybe three). There is no check for BIB.html, so we'd have to add a condition that bypasses link checking for files with that name. This is someone else's software, so we'd have to fork it and produce our own ePub validator. And I *really* don't think we can say what constitutes validity for an ePub file.