The source project of this merge request has been removed.
Docs: Merge EE doc/ci to CE
What does this MR do?
Ported to EE in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/12049.
This aligns the CE and EE doc/ci
docs, as part of the effort to combine docs into a single codebase (&199 (closed)).
This MR:
- Brings in from EE:
ci/ci_cd_for_external_repos/bitbucket_integration.md
ci/ci_cd_for_external_repos/github_integration.md
ci/ci_cd_for_external_repos/index.md
ci/metrics_reports.md
ci/multi_project_pipeline_graphs.md
ci/multi_project_pipelines.md
- Brings EE information into:
ci/interactive_web_terminal/index.md
ci/triggers/README.md
ci/variables/README.md
- Updates links in:
ci/environments.md
ci/examples/README.md
ci/examples/browser_performance.md
ci/examples/sast_docker.md
ci/pipelines.md
ci/quick_start/README.md
-
ci/yaml/README.md
(and a little EE info added as well)
- Brings in changes that were not ported from EE to CE in
ci/variables/where_variables_can_be_used.md
- Changes
ci/examples/container_scanning.md
,ci/examples/dast.md
,ci/examples/dependency_scanning.md
,ci/examples/license_management.md
andci/examples/sast.md
to redirects, (previously done in EE but not ported to CE). - All EE info seems to be properly badged (unless I'm mistaken).
When both the EE Port and this MR are merged, the doc/ci
docs should hopefully be aligned between CE and EE.
Then, please merge: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/12053, and the issue will be closed.
Related issues
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/59157
Author's checklist
-
Follow the Documentation Guidelines and Style Guide. -
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 and that you merge the equivalent EE MR before the CE MR if both exist. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by Marcel Amirault