... | @@ -479,17 +479,6 @@ content. Interestingly, it is not used for the operating system |
... | @@ -479,17 +479,6 @@ content. Interestingly, it is not used for the operating system |
|
mirrors itself, which are synchronized using another, separate system
|
|
mirrors itself, which are synchronized using another, separate system
|
|
([archvsync](https://salsa.debian.org/mirror-team/archvsync/)).
|
|
([archvsync](https://salsa.debian.org/mirror-team/archvsync/)).
|
|
|
|
|
|
The maintenance status of the mirror code is unclear: while it is
|
|
|
|
still in use at Debian.org, it is made of a few sets of components
|
|
|
|
which are not bundled in a single package. This makes it hard to
|
|
|
|
follow "upstream", although, in theory, it should be possible to
|
|
|
|
follow the [dsa-puppet](https://salsa.debian.org/dsa-team/mirror/dsa-puppet/) repository. In practice, that's pretty
|
|
|
|
difficult because the dsa-puppet and tor-puppet have disconnected
|
|
|
|
histories. Even if they would have a common ancestor, the code is
|
|
|
|
spread in multiple directories, which makes it hard to track. There
|
|
|
|
has been some refactoring to move most of the code in a `staticsync`
|
|
|
|
module, but we still have files strewn over other modules.
|
|
|
|
|
|
|
|
The static mirror system was written for Debian.org by Peter
|
|
The static mirror system was written for Debian.org by Peter
|
|
Palfrader. It has also been patches by other DSA members (Stephen
|
|
Palfrader. It has also been patches by other DSA members (Stephen
|
|
Gran and Julien Cristau both have more than 100 commits on the old
|
|
Gran and Julien Cristau both have more than 100 commits on the old
|
... | @@ -499,6 +488,32 @@ This service is critical: it distributes the main torproject.org |
... | @@ -499,6 +488,32 @@ This service is critical: it distributes the main torproject.org |
|
websites, but also software releases like the tor project source code
|
|
websites, but also software releases like the tor project source code
|
|
and other websites.
|
|
and other websites.
|
|
|
|
|
|
|
|
## Limitations
|
|
|
|
|
|
|
|
The maintenance status of the mirror code is unclear: while it is
|
|
|
|
still in use at Debian.org, it is made of a few sets of components
|
|
|
|
which are not bundled in a single package. This makes it hard to
|
|
|
|
follow "upstream", although, in theory, it should be possible to
|
|
|
|
follow the [`dsa-puppet`](https://salsa.debian.org/dsa-team/mirror/dsa-puppet/) repository. In practice, that's pretty
|
|
|
|
difficult because the `dsa-puppet` and `tor-puppet` repositories have
|
|
|
|
disconnected histories. Even if they would have a common ancestor, the
|
|
|
|
code is spread in multiple directories, which makes it hard to
|
|
|
|
track. There has been some refactoring to move most of the code in a
|
|
|
|
`staticsync` module, but we still have files strewn over other
|
|
|
|
modules.
|
|
|
|
|
|
|
|
For certain sites, the static site system requires Jenkins to build
|
|
|
|
websites, which further complicates deployments. A static site
|
|
|
|
deployment requiring Jenkins needs updates on 5 different
|
|
|
|
repositories, across 4 different services:
|
|
|
|
|
|
|
|
* a new static component in the (private) `tor-puppet.git` repository
|
|
|
|
* a [build script](https://gitweb.torproject.org/project/jenkins/tools.git/tree/slaves/linux/) in the [jenkins/tools.git](https://gitweb.torproject.org/project/jenkins/tools.git/) repository
|
|
|
|
* a build job in the [jenkins/jobs.git](https://gitweb.torproject.org/project/jenkins/jobs.git/) repository
|
|
|
|
* a [new entry](https://gitweb.torproject.org/admin/static-builds.git/commit/?id=b2344aa1d68f4f065764c6f23d14494020b81f86) in the [ssh wrapper](https://gitweb.torproject.org/admin/static-builds.git/tree/ssh-wrap?id=b2344aa1d68f4f065764c6f23d14494020b81f86) in the
|
|
|
|
[admin/static-builds.git](https://gitweb.torproject.org/admin/static-builds.git/) repository
|
|
|
|
* a new entry in the `gitolite-admin.git` repository
|
|
|
|
|
|
The static site system has no unit tests, linting, release process, or
|
|
The static site system has no unit tests, linting, release process, or
|
|
CI. Code is deployed directly through Puppet, on the live servers.
|
|
CI. Code is deployed directly through Puppet, on the live servers.
|
|
|
|
|
... | | ... | |