New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 666726 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Blocked on:
issue 539527
issue 611808

Blocking:
issue 666724



Sign in to add a comment

Further automate WebRTC rolls

Project Member Reported by phoglund@chromium.org, Nov 18 2016

Issue description

For more frequent rolls into Chrome, I would like us to consider writing a semi automated script that a sheriff could have running:
* Everything the script does, it does as the currently logged in user.
* The script assumes it 'owns' a checkout (i.e. the user does not do any work in the checkout while the script is running)
* Assuming a roll is not already in progress, the script polls for new CLs being checked in and then does one of:
  * Checking the state of the FYI builders for that revision, if all is green start a roll.
  * Prepare a roll and start a dry run.
* Once all try bots have finished, check if they're all green and the FYI bots are as well.
* Either commit or abort the roll depending on the state of the bots.
* Repeat
 
Issue 433305 has been merged into this issue.
Components: -Blink>WebRTC Infra>Client>WebRTC
Owner: kjellander@chromium.org
Status: Assigned (was: Untriaged)
I've been giving this a lot of thinking in the past, and we should really have a bot that does all this (similar to the bot we have for rolling chromium_revision in DEPS).
I created a CL for that a year ago (https://codereview.chromium.org/1384273003/) but it wasn't possible to deploy due to the LKGR not being able to incorporate the status of the chromium.webrtc + chromium.webrtc.fyi bots (which is essentially what we're talking about here with "Checking the state of the FYI builders for that revision").

I tried updating the lkgr finder in https://codereview.chromium.org/1416773007 but had to revert that, since it doesn't work as long as the got_revision property for the builders in chromium.webrtc.fyi is a Chromium revision.
Changing got_revision to be the WebRTC revision is easy, but it will have the side-effect of breaking the perf dashboard data reporting which is based on it. 

Luckily, all the above problems are very related to my Q4 OKR task of fixing the revision reporting to the perf dashboard for these bots, so I might be able to resolve it once I've gotten some time to dig into this hairy code again.

Once we get this fixed, it would be nice with an overview like https://autoroll.skia.org/ for this.
Blockedon: 611808
Cc: kjellander@chromium.org
Owner: ehmaldonado@chromium.org
Assigning to Edward since this is now a Q2 OKR. This is also blocked on getting our full Git repo into src/third_party/webrtc, which is described in go/webrtc-repo-in-chrome (tracked in  bug 611808 ).
See http://crbug.com/664042 for how to deploy credentials to slave23-c3 for the "Auto-roll - Chrome DEPS" builder once it's created.
Blockedon: 539527
I added  bug 539527  as blocking (but it's resolved) to showcase that we have an account we can use for this: webrtc-autoroll@chromium.org
Project Member

Comment 8 by bugdroid1@chromium.org, Sep 26 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/infra/infra/+/1cabe256b0fddac530e4ac0f5e8a350e172e7c63

commit 1cabe256b0fddac530e4ac0f5e8a350e172e7c63
Author: Edward Lemur <ehmaldonado@chromium.org>
Date: Tue Sep 26 14:53:47 2017

Add chromium.webrtc.fyi bots to WebRTC LKGR config.

Bug:  666726 
Change-Id: Ib171b60873d88f67bb45fddfc4a2555df9cfab17
Reviewed-on: https://chromium-review.googlesource.com/684837
Reviewed-by: Henrik Kjellander <kjellander@chromium.org>
Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org>

[modify] https://crrev.com/1cabe256b0fddac530e4ac0f5e8a350e172e7c63/infra/services/lkgr_finder/config/webrtc_cfg.pyl

Project Member

Comment 10 by bugdroid1@chromium.org, Oct 5 2017

Project Member

Comment 11 by bugdroid1@chromium.org, Oct 5 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/0770743c4d125faa22826983bbe6c8913db61447

commit 0770743c4d125faa22826983bbe6c8913db61447
Author: Edward Lemur <ehmaldonado@chromium.org>
Date: Thu Oct 05 16:27:05 2017

WebRTC: Update LKGR revision every 5 minutes.

TBR=kjellander@chromium.org

Bug:  666726 
Change-Id: Ibe4dfe022f82318c1a3badebb670fabf6a6e9a28
Reviewed-on: https://chromium-review.googlesource.com/702266
Reviewed-by: Edward Lesmes <ehmaldonado@chromium.org>
Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org>

[modify] https://crrev.com/0770743c4d125faa22826983bbe6c8913db61447/masters/master.client.webrtc.fyi/master_linux_cfg.py

Project Member

Comment 12 by bugdroid1@chromium.org, Oct 5 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/puppet/+/593ebba83d10279ac1bda5841f3ed0c4718e4af0

commit 593ebba83d10279ac1bda5841f3ed0c4718e4af0
Author: Edward Lemur <ehmaldonado@google.com>
Date: Thu Oct 05 18:20:48 2017

Status: Fixed (was: Assigned)
This is fixed, no?
Yup

Sign in to add a comment