commit | 4fd552c6af73db78a5ec395a23760a349cdb7a7b | [log] [tgz] |
---|---|---|
author | Cameron Dale <camrdale@google.com> | Thu Oct 15 18:34:51 2020 +0000 |
committer | CQ Bot <commit-bot@chromium.org> | Thu Oct 15 18:34:51 2020 +0000 |
tree | f80de36cf5e8e5d986dd1e276b0fecb6eaa96a95 | |
parent | 9766b89b8a4d100e0994f57cbd3afbb6d77fff8c [diff] |
Store all the IDs to identify a report with the observation counts. This is needed so the cobalt_testapp in Fuchsia can request the observation counts for one of the newer report IDs that are small. See fxr/439209 for these changes. Bug: 61188 Change-Id: I5b6dfb20cc3094dbbb9dd137e4a1a1a5bdcd4ef6 Reviewed-on: https://fuchsia-review.googlesource.com/c/cobalt/+/439176 Reviewed-by: Zach Bush <zmbush@google.com> Commit-Queue: Cameron Dale <camrdale@google.com>
Cobalt is a pipeline for collecting metrics data from user-owned devices in the field and producing aggregated reports.
Cobalt includes a suite of features for preserving user privacy and anonymity while giving product owners the data they need to improve their products.
The code in the Git repo at https://fuchsia.googlesource.com/cobalt is known as Cobalt Core. It contains:
In order to have a working Cobalt system you need to also have
//third_party/cobalt
.This document describes how to develop, build and test Cobalt Core independently of Fuchsia.
For example via
git clone https://fuchsia.googlesource.com/cobalt
cd cobalt
./cobaltb.py setup
This will take a few minutes the first time. It does the following:
third_party
dir via Git submodules.sysroot
dir. This uses CIPD.The Python script cobaltb.py
in the root directory is used to orchestrate building and testing Cobalt. It was already used above in ./cobaltb.py setup
.
./cobaltb.py -h
for general helpcobaltb.py <command> -h
for help on a command./cobaltb.py build
The Cobalt build uses GN and ninja.
./cobaltb.py test
./cobaltb.py fmt
./cobaltb.py lint
See: clang-tidy for an explanation of clang-tidy configuration options.
Cobalt uses the Gerrit code review tool. Although Cobalt Core is independent of Fuchsia, we do share infrastructure with Fucshia and so much of the instructions from Fuchsia's Contributing Guide apply to Cobalt Core. The main difference is that Cobalt Core does not use Jiri--it uses Git submodules instead.
Follow the instructions here.
To create a change in Gerrit do the following:
cd ~/cobalt
git checkout -b <branch_name>
git add <files>
git commit
git push origin HEAD:refs/for/master
See the Gerrit documentation for more information.
After creating a change, to upload a patch to your change, do the following:
git add <files>
--amend
option: git commit --amend
git push origin HEAD:refs/for/master