Closed Bug 1714474 Opened 3 years ago Closed 3 years ago

please create level 1 repository at l10n/gecko-strings-quarantine

Categories

(Developer Services :: Mercurial: hg.mozilla.org, task)

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: mozilla, Assigned: sheehan)

References

Details

In bug 1659691, the l10n and releng teams are working to automate cross-channel strings generation and push commits to the quarantine repository.

The current quarantine repository is a user repo of a user no longer at MoCo, which is not an ideal long-term location. I'm asking for a level 1 repo to make it simpler to push to the repo from automation. (A human will look at these commits before committing to the production strings repo.)

This could be an empty repo, or a clone of users/axel_mozilla.com/gecko-strings-quarantine/; I'm open. (I would push the contents of the latter to the new repo anyway.)

Thank you!

Initialized a new empty repo at https://hg.mozilla.org/l10n/gecko-strings-quarantine/

Level is scm_level_1. I can see some repos have a scm_l10n_infra - not sure if that's relevant in this case or not.

We should probably push the contents of the old user repo to this new repo so the pushlog is populated. :)

Assignee: nobody → sheehan
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED

Thank you! I'll check on what scm_l10n_infra is.
But when I push, I'm getting

(3.6.10:3.7.4:3.8.0:2.7.17) akimoz: ~/src/l10n/gecko-strings-quarantine (e23c50b) [11:05:18]
11090$ hg push -r . --force
pushing to ssh://hg.mozilla.org/l10n/gecko-strings-quarantine/
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: *** pushing unrelated repository ***
remote:
remote: Changeset 8de369287edd, a657f311054b, cfbbe6f3971c, f389d7a6580e introduces a new root changeset into this repository. This
remote: almost certainly means you accidentally force pushed to the wrong
remote: repository and/or URL.
remote:
remote: Your push is being rejected because this is almost certainly not what you
remote: intended.
remote: transaction abort!
remote: rollback completed
remote: pretxnchangegroup.mozhooks hook failed
abort: push failed on remote

I may need help populating this, or at least for us to disable the single_root check temporarily.

(In reply to Aki Sasaki [:aki] (he/him) (UTC-7) from comment #2)

Thank you! I'll check on what scm_l10n_infra is.

That's the group used to manage repos like l10n-central, which we need because some localizers have hg access, and should only be able to access specific repos.

Which reminds me we need to update the l10n section of this page
https://www.mozilla.org/en-US/about/governance/policies/commit/access-policy/

(In reply to Aki Sasaki [:aki] (he/him) (UTC-7) from comment #2)

I may need help populating this, or at least for us to disable the single_root check temporarily.

Looks like that was disabled for gecko-strings too (bug 1405985)

Disabled the single root check for l10n/gecko-strings-quarantine.

Status: RESOLVED → VERIFIED

Thanks Connor!

You need to log in before you can comment on or make changes to this bug.