New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 595130 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Feature



Sign in to add a comment

Archive Flash Imports to Google Storage

Project Member Reported by lafo...@chromium.org, Mar 15 2016

Issue description

Background: In order to automatically stage Flash Player components, we need to begin archiving them to a fixed Google Storage location (gs://chrome-adobe-flash-binaries).  This will allow us to pull these in automatically into OmahaRelease... and is a step towards getting us to the point where we can consider deploying Flash as an independent component.



The directory pattern would be:

<flash_version>/<platform>/...

Where <flash_version> gets replaced w/ the latest Flash Version that we import (e.g. 21.0.0.182) and platform corresponds w/ the platform directories that we are already archiving in svn (https://chromegw.corp.google.com/viewvc/chrome-internal/trunk/third_party/adobe/flash/binaries/ppapi/).


In effect, this request is basically that, when we check in the ppapi binaries into svn, we also created a mirror of those directories under a versioned directory in Google Storage.
 
Components: Internals>Plugins>Flash
Labels: Build-Official
Project Member

Comment 2 by bugdroid1@chromium.org, May 10 2016

The following revision refers to this bug:
  http://goto.ext.google.com/viewvc/chrome-internal?view=rev&revision=87672

------------------------------------------------------------------
r87672 | dimu@google.com | 2016-05-10T18:07:55.765262Z

-----------------------------------------------------------------

Comment 3 by dimu@chromium.org, Jun 28 2016

Status: Verified (was: Untriaged)

Sign in to add a comment