Commit 7c30cd16 authored by Nick Gaskill's avatar Nick Gaskill

Merge branch 'docs-ci-cd-intro-notes' into 'master'

Clean up notes at the top of ci/cd quickstart

See merge request gitlab-org/gitlab!37896
parents e4af7753 ba7a0616
...@@ -7,24 +7,6 @@ type: reference ...@@ -7,24 +7,6 @@ type: reference
# Getting started with GitLab CI/CD # Getting started with GitLab CI/CD
NOTE: **Note:**
Starting from version 8.0, GitLab [Continuous Integration](https://about.gitlab.com/stages-devops-lifecycle/continuous-integration/) (CI)
is fully integrated into GitLab itself and is [enabled](../enable_or_disable_ci.md) by default on all
projects.
NOTE: **Note:**
Please keep in mind that only project Maintainers and Admin users have
the permissions to access a project's settings.
NOTE: **Note:**
Coming over to GitLab from Jenkins? Check out our [reference](../jenkins/index.md)
for converting your pre-existing pipelines over to our format.
NOTE: **Note:**
There are a few different [basic pipeline architectures](../pipelines/pipeline_architectures.md)
that you can consider for use in your project. You may want to familiarize
yourself with these prior to getting started.
GitLab offers a [continuous integration](https://about.gitlab.com/stages-devops-lifecycle/continuous-integration/) service. For each commit or push to trigger your CI GitLab offers a [continuous integration](https://about.gitlab.com/stages-devops-lifecycle/continuous-integration/) service. For each commit or push to trigger your CI
[pipeline](../pipelines/index.md), you must: [pipeline](../pipelines/index.md), you must:
...@@ -49,7 +31,11 @@ something. ...@@ -49,7 +31,11 @@ something.
It's also common to use pipelines to automatically deploy It's also common to use pipelines to automatically deploy
tested code to staging and production environments. tested code to staging and production environments.
--- If you're already familiar with general CI/CD concepts, you can review which
[pipeline architectures](../pipelines/pipeline_architectures.md) can be used
in your projects. If you're coming over to GitLab from Jenkins, you can check out
our [reference](../migration/jenkins.md) for converting your pre-existing pipelines
over to our format.
This guide assumes that you have: This guide assumes that you have:
......
...@@ -3,7 +3,7 @@ ...@@ -3,7 +3,7 @@
NOTE: **Note:** NOTE: **Note:**
This documentation focuses only on how to **configure** a Jenkins *integration* with This documentation focuses only on how to **configure** a Jenkins *integration* with
GitLab. Learn how to **migrate** from Jenkins to GitLab CI/CD in our GitLab. Learn how to **migrate** from Jenkins to GitLab CI/CD in our
[Migrating from Jenkins](../ci/jenkins/index.md) documentation. [Migrating from Jenkins](../ci/migration/jenkins.md) documentation.
From GitLab, you can trigger a Jenkins build when you push code to a repository, or when a merge From GitLab, you can trigger a Jenkins build when you push code to a repository, or when a merge
request is created. In return, Jenkins shows the pipeline status on merge requests widgets and request is created. In return, Jenkins shows the pipeline status on merge requests widgets and
......
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