Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cl-site
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
16
Issues
16
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
clo
cl-site
Commits
122353ed
Commit
122353ed
authored
Nov 05, 2018
by
Erik Huelsmann
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Incorporate review comments
parent
38b01933
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
17 additions
and
2 deletions
+17
-2
content/faq/using-gitlab-deploy-project-pages.md
content/faq/using-gitlab-deploy-project-pages.md
+17
-2
No files found.
content/faq/using-gitlab-deploy-project-pages.md
View file @
122353ed
...
...
@@ -67,13 +67,22 @@ the site.
To prevent every intermediate result on every branch from being
deployed to your project site, the job is restricted to building
on
the `
master
` branch only, using the
from
the `
master
` branch only, using the
only:
- master
fragment.
The `
tags
` fragment mentioned below, links the job to CI builders
("runners"). Builders can only build jobs for which the job at
least one of the tags the builder has as well. On the common-lisp.net
infrastructure, this means that a job with the tag `
site-gen
` can
only be built with the builder tagged with the `
site-gen
` tag too.
tags:
- site-gen
Then, last but not least, the fragment `
script: mv src public
`
instructs the CI system to perform the "build" for this repository
(i.e. nothing more than to rename `
src
` to `
public
`).
...
...
@@ -93,9 +102,15 @@ If the syntax of your `.gitlab-ci.yml` file is correct, a new build
will run on every push or merge to the master branch. With each successful
build, a new deployment will take place.
Note that if you want to check that your `
.gitlab-ci.yml
` file has
valid syntax, you can use GitLab's "CI Lint" application. This application
is available in every project on the "Pipelines" page. For the "clo/cl-site"
project, it's located at https://gitlab.common-lisp.net/clo/cl-site/-/ci/lint
Please note that if you're migrating existing project pages from
`
/project/
<project>
/public_html
` to GitLab based deployments that
your new site won't show up until the `
public_html
`
directory has
been removed (or renamed).
For more information on how to use GitLab Pages and GitLab CI,
please see https://docs.gitlab.com/ce/user/project/pages/#overview .
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