1 # Updating Chromium's about:tracing (rolling DEPS) 2 3 Chromium's DEPS file needs to be rolled to the catapult revision containing your 4 change in order for it to appear in Chrome's about:tracing or other 5 third_party/catapult files. This should happen automatically, but you may need 6 to do it manually in rare cases. See below for more details. 7 8 ## Automatic rolls 9 10 DEPS should be automatically rolled by the auto-roll bot at 11 [catapult-roll.skia.org](https://catapult-roll.skia.org/). 12 [catapult-sheriff (a] chromium.org](https://groups.google.com/a/chromium.org/forum/#!forum/catapult-sheriff) 13 will be cc-ed on all reviews, and anyone who wants to join that list can 14 subscribe. It's also the correct list to report a problem with the autoroll. If 15 you need to stop the autoroll, either sign into that page with a google.com 16 account, or contact catapult-sheriff (a] chromium.org. 17 18 ## Manual rolls 19 20 In rare cases, you may need to make changes to chromium at the same time as you 21 roll catapult DEPs. In this case you would need to do a manual roll. Here are 22 instructions for rolling catapult DEPS, your CL would also include any other 23 changes to chromium needed to complete the roll. 24 25 First, commit to catapult. Then check the [mirror] 26 (https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git) 27 to find the git hash of your commit. (Note: it may take a few minutes to be 28 mirrored). 29 30 Then edit Chrome's [src/DEPS] 31 (https://code.google.com/p/chromium/codesearch#chromium/src/DEPS) file. Look for 32 a line like: 33 34 ``` 35 'src/third_party/catapult': 36 Var('chromium_git') + '/external/github.com/catapult-project/catapult.git' + '@' + 37 '2da8924915bd6fb7609c518f5b1f63cb606248eb', 38 ``` 39 40 Update the number to the git hash you want to roll to, and [contribute a 41 codereview to chrome](http://www.chromium.org/developers/contributing-code) 42 for your edit. If you are a Chromium committer, feel free to TBR this. 43
