tree 06b4841b976cba50dea2f567d300ae2a5b355a14
parent bb7db92ee6e788b576e22ece70914e0321a785f7
author Lorenz Brun <lorenz@nexantic.com> 1588603831 +0200
committer Lorenz Brun <lorenz@nexantic.com> 1588603831 +0200

Enable stamping and use correct variables

In D487 stamping was introduced, but not actually enabled. This enables it.

Kubernetes also uses "volatile" stamping variables for things that logic
depends on. This is a terrible idea because
you cannot unbreak a build since volatile stamps don't trigger a rebuild.
The status variables which are not purely informational have been changed
to "stable" variables
(see https://docs.bazel.build/versions/master/user-manual.html#flag--workspace_status_command).

Test Plan:
By itself not really testable, but has been tested on an
upcoming revision that actually depends on stamping behaving correctly.

X-Origin-Diff: phab/D491
GitOrigin-RevId: 48dda066d56e29d10fb0f0a88a845d8caf527c98