Git hash stamping for an external repository

[jfroy]

Description of the problem / feature request:

I need to get the git hash from a git_repository define in a WORKSPACE. Using a workspace_status_command option as described in #216 does not work, since the top level workspace ends up providing the git hash, not the external repository.

Feature requests: what underlying problem are you trying to solve with this feature?

I need to incorporate the git hash in the build because it is used as a cache validation key. It must be a github git hash because we need to be inter-operable with caches produced on other machines. The project's normal cmake build system has no problem handling this.

Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Write a genrule that consumes bazel-out/volatile-status.txt in Workspace A, import Workspace A in Workspace B using git_repository, run bazel build --workspace_status_command= with the example workspace status command (https://github.com/bazelbuild/bazel/blob/master/tools/buildstamp/get_workspace_status). The genrule will see the git hash of Workspace B, not Workspace A, even of the genrule is in Workspace A.

What operating system are you running Bazel on?

No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux rodete
Release: rodete
Codename: rodete

What's the output of bazel info release?

release 0.9.0

Have you found anything relevant by searching the web?

Mostly what is in #216, which works OK for a single workspace but not at all when using external workspaces.

[royvandam]

It looks like this information is already passed to Bazel by the _git_repository_implementation function: https://github.com/bazelbuild/bazel/blob/master/tools/build_defs/repo/git.bzl#L109

Hence I would also assume this is some how retrievable using some form of query. But I have no luck so far in figuring out how this would work. Is there someone able to elaborate if this would be feasible?

[github-actions]

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

[github-actions]

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team (@bazelbuild/triage). Thanks!