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

Issue 594002 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Make CIDB query scripts easier to use.

Project Member Reported by dgarr...@chromium.org, Mar 11 2016

Issue description

We have summarize_build_stats, and build_time_stats which pull useful data out of CIDB.

However, they both depend on installing a number of non-standard packages onto the workstation, grabbing special read-only credentials, and having a IP address which is whitelisted to contact CIDB.

It would make these tools a lot easier to use if they ran inside the chroot (hopefully auto-entering), and the chroot required everything for them to run.

Script/package wise, this isn't very hard to solve.

However, removing the CIDB whitelist and adding read only credentials to the checkout would expose all CIDB data to the world.

Is that something we could even consider? Would we consider it if the credentials only existed in an internal checkout?

 
Putting that in an internal checkout might be acceptable, at least for the readonly creds.

Actually, we have a "read only replica" instance of the database which has its own password and certificates. The creds for that I would have no problem with including in the internal checkout.
As for software dependencies, I believe they should all already exist inside the chroot.

Comment 3 by autumn@chromium.org, Mar 14 2016

Labels: -current-issue
Cc: nxia@chromium.org

Comment 5 by benhenry@google.com, Apr 26 2016

Components: Infra>Client>ChromeOS
Labels: -Infra-ChromeOS
Status: Archived (was: Untriaged)

Sign in to add a comment