Current gitlab-ci pipline defines a build for each platform.  Automated testing plan:

- build an image (for example, gce stretch)
  - stores an artifact, e.g. debian-sid-20181009-gce-amd64.zip
- local static filesystem tests
  - local-static-test.sh debian-sid-20181009-gce-amd64.zip
- local qemu live tests
  - local-live-test.sh debian-sid-20181009-gce-amd64.zip
- register/upload image to cloud provider
  - make daily builds public
  - stores an artifact with the image name
- run debian cloud tests
  - cloud-tests.sh <registered image name>
- trigger provider tests if they exist
  - GCE: daisy https://github.com/GoogleCloudPlatform/compute-image-tools
  - AWS: angry kitten (not public, but some possibility)
  - AZR: unknown github.com/LIS/LISAv2; there is internal Jenkins, but we'll probably
  use LISA; it has PowerShell control scripts and bash test scripts

For official releases, begin the manual approval/publishing step