... | @@ -372,6 +372,14 @@ rolling. For example, this will publish a `hugo` site: |
... | @@ -372,6 +372,14 @@ rolling. For example, this will publish a `hugo` site: |
|
only:
|
|
only:
|
|
- main
|
|
- main
|
|
|
|
|
|
|
|
If `.gitlab-ci.yml` already contains a job in the `build` stage that
|
|
|
|
generates the required artifacts in the `public` directory, then
|
|
|
|
including the `pages-deploy.yml` CI template should be sufficient:
|
|
|
|
|
|
|
|
include:
|
|
|
|
- project: tpo/tpa/ci-templates
|
|
|
|
file: pages-deploy.yml
|
|
|
|
|
|
GitLab pages are published under the `*.pages.torproject.org` wildcard
|
|
GitLab pages are published under the `*.pages.torproject.org` wildcard
|
|
domain. There are two types of projects hosted at the TPO GitLab:
|
|
domain. There are two types of projects hosted at the TPO GitLab:
|
|
sub-group projects, usually under the `tpo/` super-group, and user
|
|
sub-group projects, usually under the `tpo/` super-group, and user
|
... | @@ -800,6 +808,10 @@ example the status site pipeline publishes to: |
... | @@ -800,6 +808,10 @@ example the status site pipeline publishes to: |
|
Maybe this could be abused to act as a static source in the static
|
|
Maybe this could be abused to act as a static source in the static
|
|
mirror system?
|
|
mirror system?
|
|
|
|
|
|
|
|
Update: see [service/static-shim](service/static-shim) for the chosen
|
|
|
|
solution to deploy websites built in GitLab CI to the static mirror
|
|
|
|
system.
|
|
|
|
|
|
## Issues
|
|
## Issues
|
|
|
|
|
|
[File][] or [search][] for issues in the [gitlab project][search].
|
|
[File][] or [search][] for issues in the [gitlab project][search].
|
... | | ... | |