[TOC]
When chromium developers use autoninja for their build,
e.g.
$ autoninja -C out/Release chrome
autoninja uploads ninja's build log for Google employees but we don't collect logs from external contributors.
We use goma_auth info
to decide whether an autoninja user is a Googler or not.
Before uploading logs, autoninja shows a message 10 times to warn users that we will collect build logs.
autoninja users can also opt in or out by using the following commands:
ninjalog_uploader_wrapper.py opt-in
ninjalog_uploader_wrapper.py opt-out
The collected build log contains
See manual of ninja for more details.
In addition to ninja's build log, we send the following data for further analysis:
We don't collect personally identifiable information (e.g. username, ip address).
We (goma team) collect build logs to find slow build tasks that harm developer's productivity. Based on collected stats, we find the place/build tasks where we need to focus on. Also we use collected stats to track chrome build performance on developer's machine. We'll use this stats to measure how much we can/can't improve build performance on developer's machine.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。