Issue 609986 link

Starred by 1 user

Issue metadata

Status:	Duplicate
Merged:	issue 654486
Owner:	█ chenwilliam@chromium.org Last visit > 30 days ago
Closed:	Jan 2017
Cc:	█ lushnikov@chromium.org █ phajdan.jr@chromium.org █ kozyatinskiy@chromium.org dpranke@chromium.org mmoss@chromium.org
Components:	Infra>Client>Chrome
EstimatedDays:	----
NextAction:	----
OS:	Linux
Pri:	3
Type:	Bug

Upload content_shell continuous builds

Project Member Reported by lushnikov@chromium.org, May 6 2016

Issue description

Continuous chromium builds 
(http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html) now include some testing targets, such as browser_tests.

It would be great to upload content_shell as well.

A content_shell will help to:
- bisect layout test failures
- contribute to devtools front-end externally

Comment 1 by lushnikov@chromium.org, May 6 2016

Cc: mmoss@chromium.org phajdan.jr@chromium.org

Comment 2 by dpranke@chromium.org, May 6 2016

I believe that we're no longer uploading builds to chromium-browser-continuous, but chromium-browser-snapshots is still live.

the builds for the latter are created on the chromium waterfall IIUC:

https://build.chromium.org/p/chromium/builders/Linux%20x64/builds/19163/steps/archive_build/logs/stdio

I don't think it should be tricky to modify that to include content_shell.

I'm not sure who, if anyones, owns this part of the build/release process, though.