New issue
Advanced search Search tips

Issue 824898 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Aug 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: ----


Sign in to add a comment

☂ Set up a builder for frontend/WCT tests

Project Member Reported by seanmccullough@google.com, Mar 22 2018

Issue description

ChOps should run frontend tests on CQ so that our increasing amount of frontend code is automatically verified before landing.

go/chops-fe-ci is a doc describing how we can do this, and this bug is an umbrella for the subtasks to get there.

- Script to generate/update CIPD module for chrome (distributing a chrome binary with CIPD is trickier than it sounds)
- Verify that the buildbucket config for the SoM WCT Tester builder still makes sense.
- Update the sheriff-o-matic-wct recipe and wct api module to remove bower CIPD references since bower deps will be installed with bower instead of CIPD
- Rename the "Infra SoM WCT Tester" to just "WCT Tester"
- Add WCT Tester to infra’s buildbucket.config 

 
Blockedon: 824901
Blockedon: 824902
Blockedon: 824906
Blockedon: 824909
Cc: estaab@chromium.org

Comment 6 by efoo@chromium.org, Mar 28 2018

Components: -Infra Infra>Client>Chrome
Components: -Infra>Client>Chrome Infra
retriage plz also

Comment 8 by efoo@chromium.org, Mar 28 2018

Components: -Infra Infra>Sheriffing>SheriffOMatic
Labels: Milestone-Reliability
Project Member

Comment 10 by bugdroid1@chromium.org, Apr 11 2018

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

commit 038d3a1b6b4249db9e9474cbf8655f5b6aa8746f
Author: Sean McCullough <seanmccullough@chromium.org>
Date: Wed Apr 11 23:17:13 2018

[infra/tools/wct] Update wct harness to talk chrome dev protocol

This change replaces the chromedriver parts with a package that
talks directly to a chrome instance via Chrome DevTools Protocol.

This uses a package called chromedp that looks like it could
be very useful for some other automation we'd like to do. It
gives fairly fine-grained control and feedback over the browser
instance, which this CL does not really take advantage of.

Depends on some new mirrors, filed git admin ticket here:
https://bugs.chromium.org/p/chromium/issues/detail?id=829450&desc=2


Bug:  824898 
Change-Id: Ia6178b81d21c9b213dbd8ae22c5525831766fb5d
Reviewed-on: https://chromium-review.googlesource.com/998673
Commit-Queue: Sean McCullough <seanmccullough@chromium.org>
Reviewed-by: Jeff Carpenter <jeffcarp@chromium.org>

[modify] https://crrev.com/038d3a1b6b4249db9e9474cbf8655f5b6aa8746f/go/deps.lock
[modify] https://crrev.com/038d3a1b6b4249db9e9474cbf8655f5b6aa8746f/go/src/infra/tools/wct/wct.go
[modify] https://crrev.com/038d3a1b6b4249db9e9474cbf8655f5b6aa8746f/go/deps.yaml

Blocking: monorail:3698
Labels: -Pri-2 Pri-1
Owner: seanmccullough@chromium.org
Status: Started (was: Available)
Components: -Infra>Sheriffing>SheriffOMatic Infra>UI
Status: Fixed (was: Started)

Sign in to add a comment