Builds with kaniko failing

[vfarcic]

Summary

After creating a new cluster with --kaniko, quickstart projects are failing.

Steps to reproduce the behavior

jx create cluster gke \
    -n jx-rocks \
    -p $PROJECT \
    -z us-east1-b \
    -m n1-standard-2 \
    --min-num-nodes 3 \
    --max-num-nodes 5 \
    --default-admin-password=admin \
    --default-environment-prefix jx-rocks \
    --git-provider-kind github \
    --no-tiller \
    --kaniko \
    -b

jx create quickstart \
  -l go \
  -p jx-kaniko \
  -b

jx get activities -f jx-kaniko -w

STEP                         STARTED AGO DURATION STATUS
vfarcic/jx-kaniko/master #1       12m59s    3m53s Failed
  Checkout Source                 10m41s       5s Succeeded
  CI Build and push snapshot      10m35s          NotExecuted
  Build Release                   10m35s    1m28s Failed
  Promote to Environments           9m7s       0s Failed

jx get build logs vfarcic/jx-kaniko/master

...
Complete in 53.768917223s
time="2019-04-09T20:55:43Z" level=fatal msg="build failed: building [changeme]: build artifact: unknown: Project 'projects/vfarcic' not found or deleted."
...

Expected behavior

Build with kaniko should work

Actual behavior

Build with kaniko fails

Jx version

The output of jx version is:

NAME               VERSION
jx                 1.3.1096
jenkins x platform 0.0.3832
Kubernetes cluster v1.11.7-gke.12
kubectl            v1.13.2
helm client        Client: v2.12.1+g02a47c7
git                git version 2.20.1 (Apple Git-117)
Operating System   Mac OS X 10.14.4 build 18E226```

### Jenkins type

<!--
Select which Jenkins installation type are you using. 
-->
- [X] Classic Jenkins
- [ ] Serverless Jenkins

### Kubernetes cluster

GKE

### Operating system / Environment

macOS

[jenkins-x-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

[deanesmith]

/area jenkins

[jenkins-x-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

[jenkins-x-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

[jenkins-x-bot]

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.