Kustomize: Kustomize build can leave /tmp/kustomize- directories on failure

[nabadger]

I'm finding kustomize build is leaving over empty /tmp/kustomize-* directories on failed builds.

That fact these directories are empty, means it's not very useful (plus the exit error message is good enough)

A failed build can happen if you set a remote base to a non-existent git repo, or a repo that you don't have access to.

Version: {KustomizeVersion:2.0.3 GitCommit:a6f65144121d1955266b0cd836ce954c04122dc8 BuildDate:2019-03-05T20:37:42Z GoOs:linux GoArch:amd64}

Example kustomization.yaml

kind: Kustomization
apiVersion: kustomize.config.k8s.io/v1beta1

bases:
- [email protected]:nabadger/this-repo-does-not-exist.git

Results in:

Error: couldn't make loader for [email protected]:nabadger/some-invalid-repo.git: trouble cloning [email protected]:nabadger/some-invalid-repo.git: exit status 128

and after multiple runs:

$ ls -l /tmp/ | grep kustomize                                                                                                                     
drwx------ 2 nb   nb   40 May 15 20:36 kustomize-425799379
drwx------ 2 nb   nb   40 May 15 20:35 kustomize-552381152
drwx------ 2 nb   nb   40 May 15 20:36 kustomize-667894698
drwx------ 2 nb   nb   40 May 15 20:36 kustomize-855472605

[nabadger]

Related #566

[Liujingfang1]

This should have been fixed on head. Will release a new version soon.

[Liujingfang1]

Oops, just checked with v3.0.0-pre release. It's not fix yet.

[fejta-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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale