Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tor-browser-build
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 195
    • Issues 195
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • tor-browser-build
  • Issues
  • #40432

Inject commit hash into AC build.gradle files at buildtime

context

  • In a3a5306f, we added a patch to the android-components build process that prevents gradle from invoking git rev-parse to obtain the current build's commit hash (because git is absent in our build containers and invoking it will abort the build), instead simply inserting the dummy string "release build" where the hash would have occured
  • However, having the git hash in build artifacts can be quite useful for debugging later, so we'd like to preserve it, if we can.

changes

  • Inject the commit hash into the android-components build.gradle files using sed and c("abbrev") as we do in the fenix build process in 5912606f
Edited Feb 16, 2022 by aguestuser
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking