breadcrumbs:
This applies to commits to Chromium repository branches. For changes to Chromium OS repositories, see the information here.
Note: Prior to branch 3420 it is usually NOT possible to sync and build a release branch (i.e. with consistent third_party DEPS), The instructions below will only work with branch 3420 or later. For old branches, please refer to the internal documentation (go/ChromeReleaseBranches).
The first
extra # 1/2 GB or so of branch commits. gclient sync --with_branch_heads --with_tags # You may have to explicitly ‘git fetch origin’ to pull branch-heads/ git fetch
here. git checkout -b branch_$BRANCH branch-heads/$BRANCH
gclient sync --with_branch_heads --with_tags
Once checked out, building a branch should be the same as building trunk. To avoid clobbering other build artifacts, you may want to specify a different build directory (e.g. //out/Branch1234
instead of //out/Default
).
Please see the cherry-pick/drover instructions.
Note: Bugs should generally be fixed and tested on trunk (canary) and then merged to branches. However, if you cannot do that: # Make sure you are in ‘src’.
git new-branch --upstream branch-heads/$BRANCH my_hack_on_the_branch # Develop normally. git commit git cl upload
branches. git cl land
show-ref --tags')
tags/74.0.3729.131
Then build as normal.
git checkout -f master gclient sync