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

Issue 628075 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Write manifest.json files after copying Flash binaries to component archive folders

Project Member Reported by lafo...@chromium.org, Jul 14 2016

Issue description

There was a timing issue with staging flash, due to the automated staging Pipeline grabbing the files to package the crx before everything was copied over.

One potential solution would be to write the manifest.json file to each platform directory last, when we're copying, so that there is a clear signal when the copying is complete.

Meaning to change the order of archive to gs to:

1) for each platforms, upload everything but manifest.json (retaining normal directory structure)
2) for each platform, upload manifest.json
 
Cc: ananthak@chromium.org
Components: Infra>Client>Chrome>Release Internals>Plugins>Flash
Project Member

Comment 2 by bugdroid1@chromium.org, Jul 18 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/buildspec/+/5d3ffbabe8783bcecef72f228ff2935b4b1e0853

commit 5d3ffbabe8783bcecef72f228ff2935b4b1e0853
Author: Di Mu <dimu@chromium.org>
Date: Mon Jul 18 20:16:30 2016

Comment 3 by dimu@google.com, Aug 4 2016

Status: Fixed (was: Assigned)

Sign in to add a comment