Description

levlaz

opened on Nov 1, 2017

Issue body actions

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

1. zware commented on Nov 1, 2017

   

   zware

   on Nov 1, 2017

   Member

   More actions

   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.
2. levlaz commented on Nov 2, 2017

   

   levlaz

   on Nov 2, 2017

   ContributorAuthor

   More actions

   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. :)
3. willingc

   added

   type-featureAdditions; New content or section neededAdditions; New content or section needed

   on Mar 19, 2018
4. willingc commented on Mar 19, 2018

   

   willingc

   on Mar 19, 2018

   Collaborator

   More actions

   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.
5. hugovk commented on May 15, 2018

   

   hugovk

   on May 15, 2018

   Member

   More actions

   Please see PR #369.
6. willingc

   closed this as completedin #369on May 16, 2018

Issue actions