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 194
    • Issues 194
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • 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
  • #40794

Include the build-id in firefox-l10n output name

While wokring on !665 (merged), I've noticed that we don't rebuild firefox-l10n if we change the list of supported language.

It shouldn't be a big deal, because I think as a matter of fact we rarely build the same commit with a different list of locales.

However, it should be pretty easy to fix, and even a comment with the list of the included locales should suffice, I think:

# We print the locales that are included to be sure to have a new build id if we change the list
# [% tmpl(c('var/locales').join(' ')) %]

EDIT: Turns out that we weren't using build-id for firefox-l10n.

Edited Feb 21, 2023 by Pier Angelo Vendrame
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking