We've tried to satisfy the 90% case with the UI and "easy" options, especially those that transfer well from other push-to-build products.
To keep the UI simple and understandable for everyone, we decided to drop some options and require that you use a config for the more interesting cases.
There are lots of examples of config files (often named `cloudbuild.yaml`) in our github repo: https://github.com/googlecloudplatform/cloud-builders
That said, I was easily able to unblock myself because Cloud Container Builder does not actually rely on Dockerfile. You can in fact specify build steps arbitrarily, like Travis CI (or other CI services) by writing a json/yaml file. See https://cloud.google.com/container-builder/docs/api/build-re... and https://cloud.google.com/container-builder/docs/api/build-st.... In that file, you can specify what you want to build and how you want to build it. It is quite flexible.