summaryrefslogtreecommitdiff
path: root/doc/pages/README.md
diff options
context:
space:
mode:
authorAchilleas Pipinellis <axilleas@axilleas.me>2015-12-22 14:26:06 +0200
committerJames Edwards-Jones <jedwardsjones@gitlab.com>2017-01-31 22:53:56 +0000
commit8aba28e14dd7c66b17e0bc4a4230d0f5586155d0 (patch)
treef4fb3ed10bf89d59471bbcf02693aa145e14de80 /doc/pages/README.md
parent0bb480dcc738889e56397a7c05950ce8d73caedf (diff)
downloadgitlab-ce-8aba28e14dd7c66b17e0bc4a4230d0f5586155d0.tar.gz
Clarify some things in Pages [ci skip]
* Pages are enabled by default on each project * Add note about using the `only` parameter
Diffstat (limited to 'doc/pages/README.md')
-rw-r--r--doc/pages/README.md17
1 files changed, 13 insertions, 4 deletions
diff --git a/doc/pages/README.md b/doc/pages/README.md
index c83fdb63e53..ea975ec8149 100644
--- a/doc/pages/README.md
+++ b/doc/pages/README.md
@@ -17,13 +17,14 @@ The steps that are performed from the initialization of a project to the
creation of the static content, can be summed up to:
1. Create project (its name could be specific according to the case)
-1. Enable the GitLab Pages feature under the project's settings
1. Provide a specific job in `.gitlab-ci.yml`
1. GitLab Runner builds the project
1. GitLab CI uploads the artifacts
1. Nginx serves the content
As a user, you should normally be concerned only with the first three items.
+If [shared runners](../ci/runners/README.md) are enabled by your GitLab
+administrator, you should be able to use them instead of bringing your own.
In general there are four kinds of pages one might create. This is better
explained with an example so let's make some assumptions.
@@ -68,6 +69,13 @@ To make use of GitLab Pages, your `.gitlab-ci.yml` must follow the rules below:
1. Any static content must be placed under a `public/` directory
1. `artifacts` with a path to the `public/` directory must be defined
+Be aware that Pages are by default branch/tag agnostic and their deployment
+relies solely on what you specify in `gitlab-ci.yml`. If you don't limit the
+`pages` job with the [`only` parameter](../ci/yaml/README.md#only-and-except),
+whenever a new commit is pushed to whatever branch or tag, the Pages will be
+overwritten. In the examples below, we limit the Pages to be deployed whenever
+a commit is pushed only on the `master` branch, which is advisable to do so.
+
The pages are created after the build completes successfully and the artifacts
for the `pages` job are uploaded to GitLab.
@@ -84,6 +92,8 @@ pages:
artifacts:
paths:
- public
+ only:
+ - master
```
## Example projects
@@ -101,10 +111,9 @@ in the artifacts.
## Frequently Asked Questions
-**Q:** Can I download my generated pages?
+**Q: Can I download my generated pages?**
-**A:** Sure. All you need to do is download the artifacts archive from the
- build page.
+Sure. All you need to do is download the artifacts archive from the build page.
---