By default, Bazel tries not to include anything about the system state in build outputs. However, released binaries and libraries often want to include something like the version they were built at or the branch or tag they came from.
To reconcile this, Bazel has an option called the workspace status command. This command is run outside of any sandboxes on the local machine, so it can access anything about your source control, OS, or anything else you might want to include. It then dumps its output into bazel-out/volatile-status.txt, which you can use (and certain language rulesets provide support for accessing from code).
For our example, let’s suppose we’re creating fortune cookie binaries. We want each binary to be “stamped” with a different fortune, so we’ll use the
fortune command as our status. Then, our build will add “in bed” to the end of the fortune, since we’re all super mature here.
Let’s create a genrule:
genrule( name = "cookie", srcs = , outs = ["fortune-cookie"], cmd = "cat bazel-out/volatile-status.txt | grep -v BUILD_TIMESTAMP > $@; echo '...in bed.' >> $@", stamp = True, )
The most important part here is the
stamp attribute: this tells the genrule that it depends on the volatile-status.txt file. Without this attribute, the volatile-status.txt file is not a dependency of this rule, so it might not exist when the genrule is run.
cmd prints out this status. The status has a default “BUILD_TIMESTAMP” field as well, so we strip that out.
Now create a fortune-teller.sh script (and make it executable):
#!/bin/bash /usr/games/fortune -s | tr 'n' ' '
This generates short-ish fortunes and removes all of the newlines (Bazel status files are line-based, each new line is independent and written to volatile-status.txt in any order the status generator feels like).
Now we can build our fortune cookie by supplying the fortune teller to the build:
$ bazel build --stamp --workspace_status_command=$PWD/fortune-teller.sh //:cookie INFO: Found 1 target... Target //:cookie up-to-date: bazel-genfiles/fortune-cookie INFO: Elapsed time: 0.467s, Critical Path: 0.09s
Things to note:
- You must enable stamping on the command line.
- You also must pass the full path to the script, otherwise Bazel won’t find it.
Now if your take a look at bazel-genfiles/fortune-cookie:
$ cat bazel-genfiles/fortune-cookie Truth is the most valuable thing we have -- so let us economize it. -- Mark Twain ...in bed.