commit | c4af0d949294126dc690ca629ce5807d7fd03fcf | [log] [tgz] |
---|---|---|
author | Jared Weinstein <jaredweinstein@google.com> | Wed Mar 31 19:58:19 2021 +0000 |
committer | CQ Bot <commit-bot@chromium.org> | Wed Mar 31 19:58:19 2021 +0000 |
tree | 062d0aa0a96ee47fdbdcb36208611f82297d2ef2 | |
parent | 19093627ca41620ed14b1781727ff1b22e965815 [diff] |
Add BUILD_TYPE to report definition Include build type system profile field in generated observations and reports. Change-Id: Ibd4b33afa615603289fe0f12878c2b1e2eb9a34f Reviewed-on: https://fuchsia-review.googlesource.com/c/cobalt/+/508073 Reviewed-by: Zach Bush <zmbush@google.com> Fuchsia-Auto-Submit: Jared Weinstein <jaredweinstein@google.com> Commit-Queue: Auto-Submit <auto-submit@fuchsia-infra.iam.gserviceaccount.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