Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
tor-browser-build
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 192
    • Issues 192
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 7
    • Merge Requests 7
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

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.

  • The Tor Project
  • Applications
  • tor-browser-build
  • Issues
  • #30118

Closed
Open
Opened Apr 10, 2019 by boklm@boklmDeveloper

var/build_id should be stable accross build machines

The var/build_id value, which is included in filenames, is a hash of all the inputs used to create a build.

In theory this hash should be the same on different build machines. However it seems it is not always the case, at least for the android build, and we should find out why.

This command can be used to see the filename of Tor Browser alpha for android-armv7:

./rbm/rbm showconf tor-browser filename --target alpha --target torbrowser-android-armv7
Edited Oct 03, 2020 by Georg Koppen
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: tpo/applications/tor-browser-build#30118