Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set up CI with Travis #14

Open
tripu opened this issue Feb 27, 2017 · 5 comments
Open

Set up CI with Travis #14

tripu opened this issue Feb 27, 2017 · 5 comments

Comments

@tripu
Copy link
Member

tripu commented Feb 27, 2017

eg, to run tests automatically for PRs.

See docs.travis-ci.com/user/languages/perl6.

@gkellogg
Copy link
Member

I was looking into doing this for my specs using the docker image, but check-link doesn't seem to want to process a local file, only something over HTTP:

$ docker run stupchiy/checklink ./index.html
W3C Link Checker version 4.81 (c) 1999-2011 W3C
GET file:///index.html  fetched in 0.02 seconds

Error: 404 File `/index.html' does not exist

Any thoughts on doing this, short of running a separate docker instance to serve the document locally via HTTP?

@tripu
Copy link
Member Author

tripu commented Sep 17, 2018

@gkellogg: unless @stupchiy, @dontcallmedom, @tguild or @deniak have a ready answer, I recommend you check first on (and if not, write to) the www-validator mailing list.

@stupchiy
Copy link

@gkellogg, @tripu in order to test against local file, you would need to persist/share your data within container using volumes. So to accomplish that, try to execute docker command, within the folder with your index.html, this way: docker run -it --rm -v $PWD/:/test stupchiy/checklink ./test/index.html. Should be working, let me know, if not. I will adopt docs afterwards accordingly.

@dontcallmedom
Copy link
Member

I use the linkchecker on Travis CI on a regular basis for the WebRTC specs as local files - but then, I use it directly from perl, not via docker (based on the error message above, it looks like it is looking for a file at /index.html, which may be the consequence of containerization? not sure really)

@gkellogg
Copy link
Member

@stupchiy thanks for the suggestion, that does indeed work!

@dontcallmedom yes, I was going to go with the perl install, but I think it's a bit cleaner to rely on docker. There's a lot of great stuff in your Makefile that I'll take advantage of, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants