(EVERYONE) To get access to the Chromium gerrit instance:
- Go to https://chromium-review.googlesource.com/new-password
- Log in with the email you use for your git commits.
- If you are a Googler, use your @chromium.org account.
- You can verify this by ensuring that the Username field looks like git-<user>.chromium.org
- Follow the directions on the new-password page to set up/append to your .gitcookies file.
- You should click the radio button labeled "only chromium.googlesource.com" if it exists.
- Verification: Run
git ls-remote https://chromium.googlesource.com/a/chromiumos/manifest.git
- This should not prompt for any credentials, and should just print out a list of git references.
- Make sure to set your real name.
- Visit https://chromium-review.googlesource.com/#/settings/ and check the "Full Name" field.
- If it isn't set, you will need to update your Google+ profile.
- Once your Google+ profile is up-to-date, you might have to logout/login in Gerrit.
(Googler) Link @chromium.org & @google.com accounts
We use memberships of @google.com identities in particular groups to control access to Chromium repositories on chromium-review and chrome-internal-review sites. Since you will be primarily using @chromium.org account, you need to tell Gerrit that your @chromium.org and @google.com accounts are linked together. Follow the steps:
Once your accounts are linked, you'll be able to use both @chromium.org and @google.com emails in git commits. It is particularly useful if you have your @chromium.org email in global git config, and you try to trigger chrome-internal trybots (that otherwise require @google.com email).
Still having a problem?
Check out the Gerrit Documentation to see if there are hints in there.
If you have any problems please open a Build Infrastructure issue on the Chromium issue tracker (the "Build Infrastructure" template should be automatically selected).