Commit 0b1c7eea authored by Achilleas Pipinellis's avatar Achilleas Pipinellis Committed by Rémy Coutable

Test docs internal links check

parent 68aa43fd
...@@ -292,14 +292,35 @@ rake karma: ...@@ -292,14 +292,35 @@ rake karma:
paths: paths:
- coverage-javascript/ - coverage-javascript/
lint-doc: docs:check:apilint:
image: "phusion/baseimage"
stage: test stage: test
<<: *dedicated-runner <<: *dedicated-runner
image: "phusion/baseimage:latest" variables:
GIT_DEPTH: "3"
cache: {}
dependencies: []
before_script: [] before_script: []
script: script:
- scripts/lint-doc.sh - scripts/lint-doc.sh
docs:check:links:
image: "registry.gitlab.com/gitlab-org/gitlab-build-images:nanoc-bootstrap-ruby-2.4-alpine"
stage: test
<<: *dedicated-runner
variables:
GIT_DEPTH: "3"
cache: {}
dependencies: []
before_script: []
script:
- mv doc/ /nanoc/content/
- cd /nanoc
# Build HTML from Markdown
- bundle exec nanoc
# Check the internal links
- bundle exec nanoc check internal_links
bundler:check: bundler:check:
stage: test stage: test
<<: *dedicated-runner <<: *dedicated-runner
......
...@@ -14,7 +14,7 @@ Database Service (RDS) that runs PostgreSQL. ...@@ -14,7 +14,7 @@ Database Service (RDS) that runs PostgreSQL.
If you use a cloud-managed service, or provide your own PostgreSQL: If you use a cloud-managed service, or provide your own PostgreSQL:
1. Setup PostgreSQL according to the 1. Setup PostgreSQL according to the
[database requirements document](doc/install/requirements.md#database). [database requirements document](../../install/requirements.md#database).
1. Set up a `gitlab` username with a password of your choice. The `gitlab` user 1. Set up a `gitlab` username with a password of your choice. The `gitlab` user
needs privileges to create the `gitlabhq_production` database. needs privileges to create the `gitlabhq_production` database.
1. Configure the GitLab application servers with the appropriate details. 1. Configure the GitLab application servers with the appropriate details.
......
...@@ -7,7 +7,7 @@ feature tests with Capybara for integration testing. ...@@ -7,7 +7,7 @@ feature tests with Capybara for integration testing.
Feature tests need to be written for all new features. Regression tests ought Feature tests need to be written for all new features. Regression tests ought
to be written for all bug fixes to prevent them from recurring in the future. to be written for all bug fixes to prevent them from recurring in the future.
See [the Testing Standards and Style Guidelines](/doc/development/testing.md) See [the Testing Standards and Style Guidelines](../testing.md)
for more information on general testing practices at GitLab. for more information on general testing practices at GitLab.
## Karma test suite ## Karma test suite
...@@ -48,7 +48,7 @@ remove these directives when you commit your code. ...@@ -48,7 +48,7 @@ remove these directives when you commit your code.
Information on setting up and running RSpec integration tests with Information on setting up and running RSpec integration tests with
[Capybara][capybara] can be found in the [Capybara][capybara] can be found in the
[general testing guide](/doc/development/testing.md). [general testing guide](../testing.md).
## Gotchas ## Gotchas
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment