Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
b0e0dbe8
Commit
b0e0dbe8
authored
Nov 17, 2019
by
masOOd
Committed by
Ray Paik
Nov 17, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Enhance introduction/ci grammar
parent
12c8cec2
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
6 deletions
+6
-6
doc/ci/introduction/index.md
doc/ci/introduction/index.md
+6
-6
No files found.
doc/ci/introduction/index.md
View file @
b0e0dbe8
...
...
@@ -5,7 +5,7 @@ type: concepts
# Introduction to CI/CD with GitLab
In this document we'll present an overview of the concepts of Continuous Integration,
In this document
,
we'll present an overview of the concepts of Continuous Integration,
Continuous Delivery, and Continuous Deployment, as well as an introduction to
GitLab CI/CD.
...
...
@@ -31,7 +31,7 @@ to be applied according to what best suits your strategy.
### Continuous Integration
Consider an application
which
has its code stored in a Git
Consider an application
that
has its code stored in a Git
repository in GitLab. Developers push code changes every day,
multiple times a day. For every push to the repository, you
can create a set of scripts to build and test your application
...
...
@@ -94,7 +94,7 @@ To add scripts to that file, you'll need to organize them in a
sequence that suits your application and are in accordance with
the tests you wish to perform. To visualize the process, imagine
that all the scripts you add to the configuration file are the
same as the commands you run on a terminal
i
n your computer.
same as the commands you run on a terminal
o
n your computer.
Once you've added your
`.gitlab-ci.yml`
configuration file to your
repository, GitLab will detect it and run your scripts with the
...
...
@@ -121,7 +121,7 @@ Both of them compose a **pipeline** triggered at every push
to any branch of the repository.
GitLab CI/CD not only executes the jobs you've
set
,
but also shows you what's happening during execution, as you
set but also shows you what's happening during execution, as you
would see in your terminal:
![
job running
](
img/job_running.png
)
...
...
@@ -164,7 +164,7 @@ Once you're happy with your implementation:
GitLab CI/CD is capable of doing a lot more, but this workflow
exemplifies GitLab's ability to track the entire process,
without the need
of any
external tool to deliver your software.
without the need
for an
external tool to deliver your software.
And, most usefully, you can visualize all the steps through
the GitLab UI.
...
...
@@ -172,7 +172,7 @@ the GitLab UI.
If we take a deeper look into the basic workflow, we can see
the features available in GitLab at each stage of the DevOps
lifecycle, as shown
o
n the illustration below.
lifecycle, as shown
i
n the illustration below.
![
Deeper look into the basic CI/CD workflow
](
img/gitlab_workflow_example_extended_v12_3.png
)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment