Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #19363

Closed (moved)
(moved)
Open
Created Jun 09, 2016 by Iain Learmonth@irl

We should check for dead links in the website

Following on from #19359 (moved), I suspect that similar problems are present in the website.

W3C have a link checker utility that could be run from a Jenkins job.

http://search.cpan.org/dist/W3C-LinkChecker/

I have a local Jenkins instance to experiment with this. If it proves to be effective/useful we can consider moving this to jenkins.tpo.

Sebastian noted in IRC that some failures may be temporary and each failure would require individual investigation. In any documentation we should note that we should never automate fixes, even where there are permanent redirects in place (a redirect may occur simply because the content doesn't exist anymore and it just takes you to a home page for instance).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking