I spent a bit of time getting this to run. I currently get a host of 404's
and am going to need to dig in a bit and see just what they are. In the
meantime, I'm going to commit https://github.com/apache/metron/pull/1310
and have created a Jira to track adding site-book link validation to our
Travis
You will want to add a -Dlocalhost to the wget to ensure you're not
checking domains linked from our docs and turn travis into google. ;)
On Thu, Dec 20, 2018 at 3:19 PM Michael Miklavcic <
michael.miklav...@gmail.com> wrote:
> Well golly, I love this. I'll give that a whirl!
>
> On Thu, Dec 20,
Well golly, I love this. I'll give that a whirl!
On Thu, Dec 20, 2018 at 1:08 PM Casey Stella wrote:
> I definitely agree with option 3; that's a no-brainer IMO. I thought for
> sure this was already happening, honestly.
>
> As for 2, we could even script the broken link check by:
>
>- Serv
I definitely agree with option 3; that's a no-brainer IMO. I thought for
sure this was already happening, honestly.
As for 2, we could even script the broken link check by:
- Serving up the site locally via python with `python -m http.server`
from the site-book output directory
- Lookin
We recently had our site-book doc generation break due to our not including
it in the Travis build. The fix for a broken build seems simple enough -
add it to our build process and assuming it doesn't cause build timeout
issues, we should be good to go.
Beyond that, there are additional issues wit
