Repository navigation
Add linkcheck to CI #292
Description
I noticed a TODO in the .travis.yml file to add linkcheck to CI.
This is simple enough to do, is there a historical reason why it has not been done?
I noticed a TODO in the .travis.yml file to add linkcheck to CI.
This is simple enough to do, is there a historical reason why it has not been done?
Activity
zware commentedon Nov 1, 2017
I suspect it's just the fact that it would be failing, or take significant time to run. It would be worth a PR to turn it on and see what it does, but there's no guarantee that we'd merge it yet.
levlaz commentedon Nov 2, 2017
It might be useful to run the report on each build (and not cause the build to "fail") and save it as an artifact for handy reference.
It seems that in order to use artifacts on travis you need to upload them to S3 manually. Which seems not ideal.
Would you be opposed to switching to CircleCI? They host artifacts for free.
Disclaimer: I work at CircleCI. :)
willingc commentedon Mar 19, 2018
Next action: Enable linkcheck on travis as a test. Mark this test as Failure OK so that it does not prevent merges yet provides information to contributors.
hugovk commentedon May 15, 2018
Please see PR #369.