Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #34122

Closed (moved)
Open
Opened May 05, 2020 by Matthew Finkel@sysrqb

Create two Tor Browser build machines

Currently, Tor Browser developers have access to one external machine for building Tor Browser. We'd like two new build machines that are maintained by TPA. This will allow us to run parallel builds, and confirm reproducibility of the resulting builds.

The resource requirements for the machines are quite large:

  • For storage: 200GB should be an okay starting point
  • For memory: we'll need at least 16 GB.
  • For CPUs: at least two, but more would be better

The package requirements are documented here: https://gitweb.torproject.org/builders/tor-browser-build.git/tree/README#n20

apt-get install libyaml-libyaml-perl libtemplate-perl \
                  libio-handle-util-perl libio-all-perl \
                  libio-captureoutput-perl libjson-perl libpath-tiny-perl \
                  libstring-shellquote-perl libsort-versions-perl \
                  libdigest-sha-perl libdata-uuid-perl libdata-dump-perl \
                  libfile-copy-recursive-perl libfile-slurp-perl git runc \
                  mercurial

Currently, the default Tor Browser build system (tor-browser-build) requires the user have (essentially) full sudo permissions (#23631 (moved)) due to its underlying use of runc for creating deterministic build environments.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#34122