commit | 38b6dbc7939cd8b4339592d12b21c345ae29504d | [log] [tgz] |
---|---|---|
author | kjellander <kjellander@webrtc.org> | Tue Dec 13 11:35:21 2016 |
committer | Commit bot <commit-bot@chromium.org> | Tue Dec 13 11:35:28 2016 |
tree | 87987beab4dbb8c0ecd7e883c5cb813f3edb702c | |
parent | ef16e9960f47bf8150eb6782663f0be3f05e0e0a [diff] |
Autoroller: Support for rolling individual DEPS entries. Add functionality for automatic rolling of individual DEPS entries. This will make it possible to move away from the links created by setup_links.py to real DEPS entries. There are two kinds of such deps we intend to use: 1. Third party dependencies used by both WebRTC and Chromium: those are rolled to the same revision as the Chromium DEPS file of the revision passed to the script 2. Chromium sub-directories needed for WebRTC (mainly for //build and BUILD.gn files of third_party deps): those are rolled to the HEAD revision Notice that the latter kind could be rolled ahead of the chromium_revision, but generally these should be close (and if it passes the bots, we don't really mind). The new functionality can coexist with the old one, to enable a smooth transition (not everything needs to change at once). Some of the updating logic was inspired by https://cs.chromium.org/chromium/build/scripts/slave/recipes/v8/auto_roll_v8_deps.py Add extensive tests for the logic of figuring out deps changes, including mocking git ls-remote call to keep the tests hermetic. BUG=webrtc:5006 NOTRY=True Review-Url: https://codereview.webrtc.org/2570603003 Cr-Commit-Position: refs/heads/master@{#15570}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others. This page is maintained by the Google Chrome team.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.