commit | 2ea98193255ce401c5835255321e05ddf75af644 | [log] [tgz] |
---|---|---|
author | Zach Bush <zmbush@google.com> | Fri Oct 02 19:59:35 2020 +0000 |
committer | CQ Bot <commit-bot@chromium.org> | Fri Oct 02 19:59:35 2020 +0000 |
tree | ae7340215eb0f0c825c22375b4a6ca986ca9cbf6 | |
parent | 8d91e2d2f852f34835f28ff4e15c8934565e4d76 [diff] |
[roll] Roll cobalt-registry 6eb4ca7..20b0500 (3 commits) Change-Id: I75c921c6801317b381827a33bba44b9183714dd4 Reviewed-on: https://fuchsia-review.googlesource.com/c/cobalt/+/434294 Reviewed-by: Laura Peskin <pesk@google.com> Commit-Queue: Zach Bush <zmbush@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