Changes

Page history
cleanup many jenkins references authored by anarcat's avatar anarcat 
... that's as much i could do in a reasonable amount of time, but
there's a lot of references to it everywhere. There's certainly still
stuff referencing git.tpo as well.
Show whitespace changes
Inline Side-by-side
service/static-shim.md
View page @ 1e198c2b
......@@ -5,24 +5,6 @@ hosted in the [static mirror system][].
# Tutorial
## Converting a job from Jenkins
This is how to convert a given website from Jenkins to GitLab CI:
* [ ] include ci-templates `lektor.yml` job
* [ ] site builds and works in gitlab pages
* [ ] [add the deploy-static job and SSH key to GitLab CI](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/static-shim#deploying-a-static-site-from-gitlab-ci)
* [ ] [deploy the SSH key and static site in Puppet](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/static-shim#adding-a-new-static-site-shim-in-puppet)
* [ ] run the deploy-static job, make sure the site still works and
was deployed properly (`curl -sI https://example.torproject.org/ | grep -i Last-Modified`)
* [ ] [archive the repo on gitolite](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/gitlab/#how-to-migrate-a-git-repository-from-legacy-to-gitlab)
* [ ] remove the old site on staticiforme
* [ ] [fully retire the Jenkins jobs](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/jenkins#removing-a-job)
* [ ] notify users about the migration
Upstream GitLab also has [generic documentation on how to migrate from
Jenkins](https://docs.gitlab.com/ee/ci/migration/jenkins.html) which could be useful for us.
## Deploying a static site from GitLab CI
First, make sure the site builds in [GitLab CI][]. A `build` stage
......@@ -286,6 +268,28 @@ eventually be retired if that implementation is completely
removed. This logic now lives in the [`static-shim-deploy.yml`
template][].
## Converting a job from Jenkins
NOTE: this shouldn't be necessary anymore, as Jenkins was retired at
the end of 2021. It is kept for historical purposes.
This is how to convert a given website from Jenkins to GitLab CI:
* [ ] include ci-templates `lektor.yml` job
* [ ] site builds and works in gitlab pages
* [ ] [add the deploy-static job and SSH key to GitLab CI](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/static-shim#deploying-a-static-site-from-gitlab-ci)
* [ ] [deploy the SSH key and static site in Puppet](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/static-shim#adding-a-new-static-site-shim-in-puppet)
* [ ] run the deploy-static job, make sure the site still works and
was deployed properly (`curl -sI https://example.torproject.org/ | grep -i Last-Modified`)
* [ ] [archive the repo on gitolite](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/gitlab/#how-to-migrate-a-git-repository-from-legacy-to-gitlab)
* [ ] remove the old site on staticiforme
* [ ] [fully retire the Jenkins jobs](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/jenkins#removing-a-job)
* [ ] notify users about the migration
Upstream GitLab also has [generic documentation on how to migrate from
Jenkins](https://docs.gitlab.com/ee/ci/migration/jenkins.html) which could be useful for us.
## Pager playbook
A typical failure will be that users complains that their
......
......