... | ... | @@ -18,6 +18,10 @@ and the git repository: |
|
|
git clone --recursive -b main git@git-rw.torproject.org:project/web/status-site
|
|
|
cd status-site
|
|
|
|
|
|
WARNING: the URL of the Git repository changed! It used to be hosted
|
|
|
at GitLab, but is now hosted at Gitolite. The repository is *mirrored*
|
|
|
to GitLab, but pushing there will not trigger build jobs.
|
|
|
|
|
|
Then you can start a local development server to preview the site
|
|
|
with:
|
|
|
|
... | ... | @@ -44,6 +48,9 @@ integration. So you simply need to commit and push: |
|
|
git commit -a -myolo
|
|
|
git push
|
|
|
|
|
|
Note that only the `webwml` group has access to the repository for
|
|
|
now.
|
|
|
|
|
|
You will see progress of the Jenkins jobs:
|
|
|
|
|
|
* [hugo-website-status](https://jenkins.torproject.org/job/hugo-website-status/) (build job)
|
... | ... | @@ -52,9 +59,12 @@ You will see progress of the Jenkins jobs: |
|
|
If all goes well, the changes should propagate to the mirrors within
|
|
|
about 5 to 10 minutes, depending on how busy Jenkins is.
|
|
|
|
|
|
Note that only the `webwml` group has access to the repository for
|
|
|
now. Merge requests may also be issued from the mirror of the
|
|
|
repository on GitLab:
|
|
|
If the jobs did not trigger, make sure you are pushing to the Gitolite
|
|
|
server (`git-rw.torproject.org`) and *NOT* the GitLab server, which is
|
|
|
just a mirror and cannot currently trigger Jenkins jobs.
|
|
|
|
|
|
Merge requests may also be issued from the mirror of the repository on
|
|
|
GitLab:
|
|
|
|
|
|
<https://gitlab.torproject.org/tpo/tpa/status-site>
|
|
|
|
... | ... | |