AvaloniaUI
/
angle
зеркало из https://github.com/AvaloniaUI/angle.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
angle/infra
История
Michael Spang a32a0bef6d Add fuchsia-angle-rel to the CQ 
Unlike fuchsia_x64, this trybot builds with angle_top_of_tree, and won't
cause random patch failures.

Bug: angleproject:3146

Change-Id: Iea8f93c7e3b6c4bf4514a9c0c6eacca9bd3228c8
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1611730
Commit-Queue: Michael Spang <spang@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
 		2019-05-15 00:17:55 +00:00
..
config Add fuchsia-angle-rel to the CQ 2019-05-15 00:17:55 +00:00
ANGLEWrangling.md Minor update to auto-roller infra docs. 2019-04-10 17:09:31 +00:00
README.md Update docs on wrangling and standalone infra. 2019-01-28 22:04:38 +00:00

README.md

ANGLE Standalone Testing Infrastructure

In addition to the ANGLE try bots using Chrome, and the GPU.FYI bots, ANGLE has standalone testing on the Chrome infrastructure. Currently these tests are compile-only. This page is for maintaining the configurations that don't use Chromium. Also see the main instructions for ANGLE Wrangling.

It's the ANGLE team's responsibility for maintaining this testing infrastructure. The bot configurations live in four different repos and six branches.

Info Consoles

Continuous builders for every ANGLE revision are found on the CI console:

https://ci.chromium.org/p/angle/g/ci/console

Try jobs from pre-commit builds are found on the builders console:

https://ci.chromium.org/p/angle/g/try/builders

How to add a new build configuration

  1. bugs.chromium.org/p/chromium/issues/entry?template=Build+Infrastructure:

    • Request new slaves by filing an infra issue.

  2. chromium.googlesource.com/chromium/tools/build:

    • Update scripts/slave/recipes/angle.py with new the config.
    • The recipe code requires 100% code coverage through mock bots, so add mock bot config to GenTests.
    • Maybe run ./scripts/slave/recipes.py test train to update checked-in golden files. This might no longer be necessary.

  3. chrome-internal.googlesource.com/infradata/config:

    • Update configs/chromium-swarm/bots.cfg to map from the slaves requested in step 1 to the builder configured in step 2.

  4. chromium.googlesource.com/angle/angle:

    • Update infra/config/global/cr-buildbucket.cfg to add the new builder (to ci and try), and set the new config option.
    • Update infra/config/global/luci-milo.cfg to make the builders show up on the ci and try waterfalls.
    • Update infra/config/global/luci-scheduler.cfg to make the builders trigger on new commits or try jobs respectively.
    • Update infra/config/cq.cfg to add the builder to the default CQ jobs (if desired).

Other Configuration

There are other places where configuration for ANGLE infra lives. These are files that we shouldn't need to modify very often:

  1. chrome-internal.googlesource.com/infradata/config:

    • configs/luci-token-server/service_accounts.cfg (service account names)
    • configs/chromium-swarm/pools.cfg (swarming pools)

  2. chromium.googlesource.com/chromium/tools/depot_tools:

    • recipes/recipe_modules/gclient/config.py (gclient config)