PSA: [Action required] Generate .netrc password for git access

[Vadim Shtayura]

Hello Chromium Developers,

In the future you will need a chromium.googlesource.com token in your ~/.netrc file to commit 

to the Chromium git repository.

It may already be there. In your ~/.netrc file (%HOME%/_netrc on Windows) search for

a line that looks like this:

machine chromium.googlesource.com login git-<userid>.chromium.org password <token>

(For googlers: ‘login git-<userid>.google.com‘ is also OK)

If the line is not there (or a netrc file doesn’t exist), please do the following:

1. Go to https://chromium.googlesource.com/new-password

2. Login with your @chromium.org account.

3. Follow the instructions in the "Staying Authenticated" section.

Later we will be adding a gclient hook to src/DEPS that verifies that all committers have push access to the Chromium git repository. There will be a separate PSA about that.

Thanks!

[Yuzhu Shen]

On Mon, Aug 11, 2014 at 3:14 PM, Vadim Shtayura <vad...@chromium.org> wrote:

Hello Chromium Developers,

In the future you will need a chromium.googlesource.com token in your ~/.netrc file to commit 

to the Chromium git repository.

It may already be there. In your ~/.netrc file (%HOME%/_netrc on Windows) search for

a line that looks like this:

machine chromium.googlesource.com login git-<userid>.chromium.org password <token>

(For googlers: ‘login git-<userid>.google.com‘ is also OK)

If the line is not there (or a netrc file doesn’t exist), please do the following:

1. Go to https://chromium.googlesource.com/new-password

Does every visit to this page invalidate previous passwords?

(If yes, it is a little inconvenient because I need to set this on multiple machines.)

 

2. Login with your @chromium.org account.

3. Follow the instructions in the "Staying Authenticated" section.

Later we will be adding a gclient hook to src/DEPS that verifies that all committers have push access to the Chromium git repository. There will be a separate PSA about that.

Thanks!

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Vadim Shtayura]

No, it doesn't invalidate previous passwords. 

There's a separate page "Revoke prior passwords" for that, see top right corner of https://chromium.googlesource.com .

[Yoav Weiss]

On Tue, Aug 12, 2014 at 12:14 AM, Vadim Shtayura <vad...@chromium.org> wrote:

Hello Chromium Developers,

In the future you will need a chromium.googlesource.com token in your ~/.netrc file to commit 

to the Chromium git repository.

It may already be there. In your ~/.netrc file (%HOME%/_netrc on Windows) search for

a line that looks like this:

machine chromium.googlesource.com login git-<userid>.chromium.org password <token>

 

Will this also work for those of us who don't use a chromium.org address?

 

(For googlers: ‘login git-<userid>.google.com‘ is also OK)

If the line is not there (or a netrc file doesn’t exist), please do the following:

1. Go to https://chromium.googlesource.com/new-password

2. Login with your @chromium.org account.

3. Follow the instructions in the "Staying Authenticated" section.

Later we will be adding a gclient hook to src/DEPS that verifies that all committers have push access to the Chromium git repository. There will be a separate PSA about that.

Thanks!

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

[Vadim Shtayura]

On Mon, Aug 11, 2014 at 10:56 PM, Yoav Weiss <yo...@yoav.ws> wrote:

On Tue, Aug 12, 2014 at 12:14 AM, Vadim Shtayura <vad...@chromium.org> wrote:

Hello Chromium Developers,

In the future you will need a chromium.googlesource.com token in your ~/.netrc file to commit 

to the Chromium git repository.

It may already be there. In your ~/.netrc file (%HOME%/_netrc on Windows) search for

a line that looks like this:

machine chromium.googlesource.com login git-<userid>.chromium.org password <token>

 

Will this also work for those of us who don't use a chromium.org address?

Yes. But I think it should be "Google Apps for Your Domain" account (i.e. ultimately the account is managed and known by google). Try to login to https://chromium.googlesource.com/new-password to verify.

[Thiago Farina]

On Mon, Aug 11, 2014 at 7:14 PM, Vadim Shtayura <vad...@chromium.org> wrote:

Hello Chromium Developers,

In the future you will need a chromium.googlesource.com token in your ~/.netrc file to commit 

to the Chromium git repository.

I don't think I have a .netrc in my home directory.

How it look like?

Are this documented somewhere in chromium.org, not just a PSA in blink-dev and chromium-dev?

--

Thiago Farina

[Torne (Richard Coles)]

If you don't have one, create one (and make sure its permissions are 0600 as many programs refuse to read .netrc files which are readable by anyone other than you). The instructions on the password generation page should mention this.

[Jeremy Roman]

On Tue, Aug 12, 2014 at 11:52 AM, Thiago Farina <tfa...@chromium.org> wrote:

I don't think I have a .netrc in my home directory.

How it look like?

As the PSA says, https://chromium.googlesource.com/new-password will give you the correct contents. It looks like:

machine chromium.googlesource.com login git-yourusernamehere.chromium.org password anautogeneratedpasswordhere

machine chromium-review.googlesource.com login git-yourusernamehere.chromium.org password anautogeneratedpasswordhere

 

Are this documented somewhere in chromium.org, not just a PSA in blink-dev and chromium-dev?

It is mentioned in the experimental branch setup page, but +1 to documenting it elsewhere.

It sounds like this will replace the SVN setup instructions at http://www.chromium.org/developers/how-tos/get-the-code.

[Vadim Shtayura]

Added a section about .netrc setup to https://sites.google.com/a/chromium.org/dev/developers/how-tos/get-the-code (in "Initial Checkout" section).