Add option to download reference build from internal storage.

Add option to download reference build from internal storage.

The Google storage is not always up-to-date with official build. This CL
downloads official builds by default from internal storage (requires corp)
net. 
Added --gs option to download from gs://.

BUG=302065
NOTRY=true

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=231165

[shadi, 2013-10-21 18:35:59]

Tony, it appears the gs:// bucket is not updated frequently. I was not able to
find M30 build post r221697 for example. So, I added the option to download from
internal storage.

PS: originally, I chose gs:// so that bots later can download official builds
w/o corp net.

[tonyg, 2013-10-21 19:20:05]

https://codereview.chromium.org/33353002/diff/1/tools/update_reference_build.py
File tools/update_reference_build.py (right):

https://codereview.chromium.org/33353002/diff/1/tools/update_reference_build....
tools/update_reference_build.py:43: 'official_builds/%s/%s/%s')
I'm not sure we should check in a corp url. Can we make a go-link?

[shadi, 2013-10-21 19:53:53]

PTAL

https://codereview.chromium.org/33353002/diff/1/tools/update_reference_build.py
File tools/update_reference_build.py (right):

https://codereview.chromium.org/33353002/diff/1/tools/update_reference_build....
tools/update_reference_build.py:43: 'official_builds/%s/%s/%s')
On 2013/10/21 19:20:06, tonyg wrote:
> I'm not sure we should check in a corp url. Can we make a go-link?

Done.

[shadi, 2013-10-23 22:41:35]

PTAL

https://codereview.chromium.org/33353002/diff/90001/tools/update_reference_bu...
File tools/update_reference_build.py (right):

https://codereview.chromium.org/33353002/diff/90001/tools/update_reference_bu...
tools/update_reference_build.py:44: 'official_builds/%s/%s/%s')
I was not able to bypass login requirements with goto links. A wget on a goto
link works but urllib2.urlopen will get the login screen.

[tonyg, 2013-10-23 23:16:56]

Justin, is it okay to check in this URL? Any ideas for avoiding it?

The rest of this change lg2m

[jschuh, 2013-10-23 23:34:37]

On 2013/10/23 23:16:56, tonyg wrote:
> Justin, is it okay to check in this URL? Any ideas for avoiding it?
> 
> The rest of this change lg2m

I'm not sure on this one. I'd ask someone on infrastructure or release. I just
pinged @laforge, so maybe he'll drive-by.

[jschuh, 2013-10-24 00:07:47]

On 2013/10/23 23:34:37, Justin Schuh wrote:
> On 2013/10/23 23:16:56, tonyg wrote:
> > Justin, is it okay to check in this URL? Any ideas for avoiding it?
> > 
> > The rest of this change lg2m
> 
> I'm not sure on this one. I'd ask someone on infrastructure or release. I just
> pinged @laforge, so maybe he'll drive-by.

Okay, according to @laforge this cat is already well out of the bag, so lgtm.

[shadi, 2013-10-25 21:36:15]

On 2013/10/24 00:07:47, Justin Schuh wrote:
> On 2013/10/23 23:34:37, Justin Schuh wrote:
> > On 2013/10/23 23:16:56, tonyg wrote:
> > > Justin, is it okay to check in this URL? Any ideas for avoiding it?
> > > 
> > > The rest of this change lg2m
> > 
> > I'm not sure on this one. I'd ask someone on infrastructure or release. I
just
> > pinged @laforge, so maybe he'll drive-by.
> 
> Okay, according to @laforge this cat is already well out of the bag, so lgtm.

tonyg@: any further concerns?

[tonyg, 2013-10-25 22:12:56]

lgtm

[commit-bot: I haz the power, 2013-10-26 00:24:01]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/shadi@chromium.org/33353002/90001

[commit-bot: I haz the power, 2013-10-26 00:28:40]

Change committed as 231165