d2320cee87
The baremetal machines rarely catch any issues that are caught by the other bots and are currently the bottleneck of the CQ. Since they still run in client.webrtc and there also produces perf data, I think it makes sense to exclude them from the CQ. It is still possible to run tryjobs on them using: git try --bot=linux_baremetal --bot=win_baremetal --bot=mac_baremetal R=phoglund@webrtc.org Review URL: https://codereview.webrtc.org/1349013004 . Cr-Commit-Position: refs/heads/master@{#9970}
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.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://chromium.googlesource.com/external/webrtc
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc