The fixes involve upgrading to a newer version of Prow and Knative Build, the latter caused an issue when performing a traditional jx upgrade addon so we recommend uninstalling Knative Build first (removes Knative Build related Custom Resource Definitions) and install the latest release.
jx delete addon knative-build
And to be extra sure it’s gone maybe do an extra:
helm del --purge knative-build
jx upgrade cli
jx upgrade addon prow
But this means any existing builds or custom changes to BuildTemplate resources will be lost.
5 Jan 2019: environment git repository issue
There was a regression added a few weeks ago which led to new installations setting up invalid exposecontroller configuration in your Staging/Production git repositories. See the issue and workaround
Make sure that the env/values.yaml file for your environment git repository uses expose: as the key in the YAML and not exposecontroller: - if it uses exposecontroller: just edit it back to expose: and you should be good to go!
Also we have noticed a possible regression with helm where if you have multiple expose: sections in your environment env/values.yaml it can disable the exposecontroller post install helm hook which can break the creation of Ingress resources in your environment - if you have more than one expose: sections please combine them into a single entry