Releaser incorrectly tags images as "dirty"

[jlewi]

The releaser is tagging our images as dirty; e.g.

gcr.io/tf-on-k8s-dogfood/tf_operator:v20180117-04425d9-dirty-e3b0c44

Probably because we modify some files in the git source tree as part of a build.

We should fix this.

[jlewi]

See #339 for discussion about how we want to start tagging our releases.

[jose5918]

@jlewi Mind if I take this? I found this was being tagged as dirty as a result of glide install. Making an adjustment to how we check modified files like this: git ls-files *[^vendor/*] --modified or git ls-files --modified | grep -v ^vendor should make it stop tagging as dirty. Does that seem like a valid solution?

Also I haven't tried with airflow or anything but the earliest release I see tagged as dirty gs://tf-on-k8s-dogfood-releases/v20171218-c8bcb9d-dirty-e3b0c44/ matches the pr that added vendor #222

[jlewi]

That would be great thanks.

[jlewi]

This is obsolete since we are moving to using an Argo workflow to build images and that doesn't appear to have this problem.