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
0
Merge Requests
0
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
Tatuya Kamada
gitlab-ce
Commits
149c934a
Commit
149c934a
authored
Dec 08, 2015
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
More cleanup on Redis example
parent
4236861d
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
4 deletions
+4
-4
doc/ci/services/redis.md
doc/ci/services/redis.md
+4
-4
No files found.
doc/ci/services/redis.md
View file @
149c934a
...
...
@@ -4,10 +4,10 @@ As many applications depend on Redis as their key-value store, you will
eventually need it in order for your tests to run. Below you are guided how to
do this with the Docker and Shell executors of GitLab Runner.
## Use Redis with Docker executor
## Use Redis with
the
Docker executor
If you are using
our Docker integration you basically have everything set up
already.
If you are using
GitLab's Runner Docker integration you basically have
everything set up
already.
First, in your
`.gitlab-ci.yml`
add:
...
...
@@ -29,7 +29,7 @@ framework.
If you want to use any other version of Redis, check the available versions
on
[
Docker Hub
](
https://hub.docker.com/_/redis/
)
.
## Use Redis with Shell executor
## Use Redis with
the
Shell executor
Redis can also be used on manually configured servers that are using GitLab
Runner with the Shell executor.
...
...
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