The Chromium Projects

Search this site

Except as otherwise noted, the content of this page is licensed under a Creative Commons Attribution 2.5 license, and examples are licensed under the BSD License.
For Developers‎ > ‎How-Tos‎ > ‎

Quick Reference

Fix Build Break

When your patch brakes build, commit bot send you email. You should do
  1. Update build console status (http://build.chromium.org/p/chromium/console) from http://chromium-status.appspot.com
    • It seems background color of status message is determined by word "close"(to read), "open"(to green), otherwise(to yellow.)
  2. Revert your change by using Drover (How to use drover)
    • Example: Your patch revision 123456
    • drover --revert 123456
  3. Watching commit progress then update build console status

Fix Compilation Failure on chromeos trybot

  1. Remove out put files, e.g. rm -rf out
  2. Run GYP_DEFINES="chromeos=1" gclient runhooks
  3. Run make chromeos_builder

Fix Compilation Failure on linux_view trybot
  1. Remove out put files, e.g. rm -rf out
  2. Run GYP_DEFINES="toolkit_views=1" gclient runhooks
  3. Run make

Merge to Release Branch

When you think your change should be into release branch, you should get approval from release manager from http://crbug.com (add Mstone-XX and Merge-Requested label, then send email to release manager)
  1. Check branch-id of milestone from http://src.chromium.org/viewvc/chrome/releases/
  2. Create empty directory for drover work space, e.g. ~/drover
    • Drover downloads files related to your patch from SVN tree into directory drover_123456_876.
  3. Run drover in drover work space
    • Example:
    • Branch 15.0.876.0
    • Revision 123456
    • drover --branch 876 --merge 123456
  4. Check result in http://crbug.com

Comments