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
2c30d11e
Commit
2c30d11e
authored
Nov 05, 2015
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Clean up intro
parent
5f6117c0
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
doc/ci/quick_start/README.md
doc/ci/quick_start/README.md
+2
-2
No files found.
doc/ci/quick_start/README.md
View file @
2c30d11e
...
...
@@ -16,8 +16,8 @@ In brief, the steps needed to have a working CI can be summed up to:
1.
Configure a Runner
From there on, on every push to your git repository the build will be
automagically started by the
Runner and will appear under the project's
`/builds`
page.
automagically started by the
runner and will appear under the project's
`/builds`
page.
Now, let's break it down to pieces and work on solving the GitLab CI puzzle.
...
...
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