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

Run make linkcheck in CI #724

Closed
minrk opened this issue Jun 14, 2018 · 15 comments
Closed

Run make linkcheck in CI #724

minrk opened this issue Jun 14, 2018 · 15 comments

Comments

@minrk
Copy link
Member

minrk commented Jun 14, 2018

There are quite a few broken links in our docs. We can and probably should be running make linkcheck in the docs as part of CI.

cc @willingc

Related to #723

@willingc
Copy link
Collaborator

Absolutely agree. Thanks @minrk.

@willingc
Copy link
Collaborator

Just did a make linkcheck. There are about 8 broken links and a number of redirects to new locations. I'm at Cal Poly today and will try to do a cleanup of the links and then add the linkcheck to Travis.

@choldgraf
Copy link
Member

ah this is a great idea

@consideRatio
Copy link
Member

❤️
It may also be good to have tools/lint.py run, it is on my long term todo list. Currently I run it manually from time to time.

@willingc
Copy link
Collaborator

willingc commented Jul 2, 2018

If we run a linter, we should also start using black for Python code for style (over time).

@consideRatio
Copy link
Member

Ah deal @willingc I'll look into that! It is currently only linting yaml and verifying it makes sense with kubernetes resource specifications.

@consideRatio
Copy link
Member

In #758 i added tools/lint.py which i should now rename to lint-and-validate-k8s-yaml.py as part of the CI.

@willingc you seem to be in the know of how to do this, could you add a make linkcheck to the CI?

@consideRatio consideRatio added this to the 0.7 milestone Jul 21, 2018
@consideRatio consideRatio modified the milestones: 0.7, 0.8 Aug 18, 2018
@consideRatio
Copy link
Member

Bumping this, I'd love to see this now that we are making additional changes to the docs.

Looked at whats going on in the makefiles etc, but didn't quickly conclude what I needed to do.
https://github.com/jupyterhub/jupyterhub/blob/4d2d677777ef63f466934376d726cd6130df4a34/docs/make.bat

@consideRatio consideRatio removed this from the 0.8 milestone Dec 20, 2018
@choldgraf
Copy link
Member

is this now just a matter of adding make linkcheck into one of our travis/circle builds?

@consideRatio
Copy link
Member

Hmmm, I think it will fail without proper reason due to "missing anchor" stuff that actually works though.

If we make it make linkcheck || true then we get the info without the crash on failure. I'm not confident about the make linkcheck as part of the CI though, as it often does not happen as a consequence of a new PR's code itself but simply becoming outdated.

Seems like we should check internal references rather than external, hmmm, perhaps make linkcheck also requires us to first do make html, right?

@choldgraf
Copy link
Member

ah I see - perhaps something to just do as a "team process" kind of thing once in a while? Or is there a way to make the anchor links pass?

@consideRatio
Copy link
Member

@choldgraf I don't know - I did not investigate it though.

@manics
Copy link
Member

manics commented Jan 3, 2019

Could you add a Travis cron job so you'll know if the master branch breaks?

@consideRatio
Copy link
Member

Sounds great @manics !!!

@consideRatio
Copy link
Member

We now have a linkcheck running that provide output on build, it has typically failed almost nonstop, but at the same time I've caught a lot of things thanks to it!

Thanks @manics!

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

5 participants