Google Git
Sign in
skia / buildbot / e67e3308fac953ad0a832a295c54bd21ab7da726 / . / docker_pushes_watcher
tree: f343153d4eeb35be294e2ddc2d0baed25f5010d7 [path history] [tgz]
  1. go/
  2. build_docker_release
  3. create-sa.sh
  4. Dockerfile
  5. FIRESTORE.md
  6. Makefile
  7. README.md
docker_pushes_watcher/README.md

Docker Pushes Watcher

Docker pushes watcher is an app that with new task drivers and new jobs has replaced Google Cloud Build for Skia. The tracking bug for this work was skbug/9514.

Previous Cloud Build framework

Skia used to trigger builds on Google Cloud's Cloud Build framework using this cloudbuild.yaml file.

Using cloud build, the “skia-release” and “skia-wasm-release” images were created and pushed per commit in the Skia repository. The “infra” image was created and pushed per commit in the Buildbot repository.

Additionally cloudbuild.yaml created and pushed new images for various apps like fiddler, skottie, particles, debugger, etc.

The continuous-deploy app then ran pushk on those apps and deployed them to k8s.

Replacement framework with Task Drivers and Docker Pushes Watcher app

The Cloud build framework worked but did not use Skia infra framework and was thus difficult to see failures and diagnose problems. The framework was replaced with task drivers and the docker-pushes-watcher app.

Now all failures when building apps cause the corresponding jobs to turn red on status.skia.org for the commits that break things, this makes failures much easier to find for the Skia Gardener. Failures in the docker-pushes-watcher app show up as alerts for the Infra Gardener to diagnose and fix.

Task Drivers

A task driver was written to build and push a specified docker image (build_push_docker_image).

The following jobs were then created in the different repositories:

These jobs could run out of order because of backfilling. Due to this the “Docker Pushes Watcher” app (described below) calculates which image is the most recent and then tags it with the “prod” tag.

Task Drivers were also written to create and push Docker images of various apps that depend on the “gcr.io/skia-public/skia-release” and “gcr.io/skia-public/skia-wasm-release” images:

The following jobs were created in the Skia repo using the above task drivers:

All above task drivers send a pubsub message when a docker image is created and pushed.

Docker Pushes Watcher App

The docker pushes watcher app listens for pubsub messages for 2 main tasks:

  • Tags images in the app's list with the “prod” tag when they correspond to the latest commit in the Skia/Buildbot repository. This is done to account for jobs running out of order because of backfilling.
  • Deploys apps to k8s using pushk for images in the app's list when they correspond to the latest commit.

Auto-deploying infra apps

A task driver has been written to build and push images of infra apps (push_apps_from_infra_image). The task driver sends a pubsub message after it builds the image; the docker_pushes_watcher app then calls pushks on those images. Pushk finds the apps that use those images, updates the current version of the images and deploys them.

Setting up auto-deploy for a new app

  1. Add a new method to the task_driver, similar to buildPushCTImage.
  2. Add the image used by the app to the docker_pushs_watcher yaml file (example).
  3. Use pushk manually to push a clean version of the given image (docker_pushes_watcher will not override dirty images). e.g. pushk gcr.io/skia-public/debugger-app:2020-11-13T14_50_19Z-kjlubick-fcd8c1a-clean