diff options
| author | Mark Pundsack <mpundsack@gitlab.com> | 2017-02-06 17:36:34 -0600 |
|---|---|---|
| committer | Mark Pundsack <mpundsack@gitlab.com> | 2017-02-06 17:36:34 -0600 |
| commit | 2338aa6a25ae07b6c00841431264fb02f77db36a (patch) | |
| tree | 1763812e414bcfebc48637b72ef0133b9c3005b1 | |
| parent | 4a38a3bb2fc0abaad175d9287e17998b6c5bb93b (diff) | |
| download | gitlab-ce-2338aa6a25ae07b6c00841431264fb02f77db36a.tar.gz | |
Add image titles
| -rw-r--r-- | doc/ci/pipelines.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/ci/pipelines.md b/doc/ci/pipelines.md index 0a9f4631614..35a80dd2977 100644 --- a/doc/ci/pipelines.md +++ b/doc/ci/pipelines.md @@ -17,7 +17,7 @@ executed. There are three types of pipelines that often use the single shorthand of "pipeline". People often talk about them as if each one is "the" pipeline, but really, they're just pieces of a single, comprehensive pipeline. - + 1. **CI Pipeline**: Build and test stages defined in `.gitlab-ci.yml` 2. **Deploy Pipeline**: Deploy stage(s) defined in `.gitlab-ci.yml` The flow of deploying code to servers through various stages: e.g. development to staging to production @@ -31,7 +31,7 @@ Pipelines accommodate several development workflows: 2. **Trunk-based Flow** (e.g. feature branches and single master branch, possibly with tags for releases) 3. **Fork-based Flow** (e.g. merge requests come from forks) -Example flow: +Example continuous delivery flow:  |