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

Issue 833664 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Sep 26
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 829522
issue 834073
issue 834074



Sign in to add a comment

chromeos.branch/chromeos.release and metadata.json

Project Member Reported by dgarr...@chromium.org, Apr 16 2018

Issue description

Golden Eye extracts part of it's information about a build from a metadata.json file uploaded along with build artifacts. A "branch" value was only recently added to this file.

Before transitioning release waterfall builds, we need to merge this CL:894844 back to the active release branches.

Before transitioning chromeos.branch builds, we need to invent a better solution. Merging back to all of this is not practical, and many of the older firmware builders upload very old versions of metadata.json, or may not upload it at all.
 
Blocking: 834073
Blocking: 834074
Blocking: 829522
Components: -Infra>Client>ChromeOS Infra>Client>ChromeOS>CI
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
Status: Fixed (was: Assigned)
I believe this is solved for all active release branches, and will be solved for all firmware branches by the "firmwarebranch" builders. A similar solution for factory builds is already planned.

Sign in to add a comment