Use the 'ee/' path to build the Nanoc site
What does this MR do?
Use the 'ee/' path to build the Nanoc site.
We can do this now that we have merged CE/EE, the $DOCS_GITLAB_REPO_SUFFIX variable
is no longer needed.
The following merge requests fixed a bug we had in the docs pipeline:
but introduced another.
Namely, forks cannot use the project-set $DOCS_GITLAB_REPO_SUFFIX
variable, so they will fail at the internal links test. For example
https://gitlab.com/briankabiro/gitlab-ee/-/jobs/460294523.
Nanoc would create the content under 'public/doc/', whereas it should be 'public/ee/', since we have some hardcoded links set in https://gitlab.com/gitlab-org/gitlab-docs/-/blob/887850752fc0e72856da6632db132f005ba77f16/content/index.erb#L44-63
Related issues
Fixes #209060 (closed)
Author's checklist
-
Follow the Documentation Guidelines and Style Guide. -
If applicable, update the permissions table. -
Link docs to and from the higher-level index page, plus other related docs where helpful. -
Apply the documentation label.
Review checklist
All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.
1. Primary Reviewer
-
Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
2. Technical Writer
-
Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
3. Maintainer
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.