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
  • #24879

Closed (moved)
Open
Opened Jan 12, 2018 by boklm@boklm

Set 'fetch: 1' by default for nightly builds

In tor-browser-build, when doing some build, we fetch new commits/branchs/tags from a git repository when the git revision specified in git_hash does not exist in the local repository. If the revision already exist, we don't update the repository. This means that if git_hash is pointing to a branch like master and the master branch already exists, it won't be updated. This can be confusing for the nightly builds, where you have to remember to run make fetch first if you want to build the very latest nightly, and not a nightly based on the commits from the last make fetch.

To avoid that we can set fetch: 1 for nightly in rbm.conf so that git repositories are updated for each build by default. People who don't want that can still change it in their rbm.local.conf.

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#24879