Archive Flash Imports to Google Storage |
||
Issue descriptionBackground: 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.
,
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 -----------------------------------------------------------------
,
Jun 28 2016
|
||
►
Sign in to add a comment |
||
Comment 1 by lafo...@chromium.org
, Mar 15 2016Labels: Build-Official