summaryrefslogtreecommitdiffstats
path: root/manifest_xml.py
diff options
context:
space:
mode:
authorSean McAllister <smcallis@google.com>2020-04-15 12:24:43 -0600
committerSean McAllister <smcallis@google.com>2020-04-16 18:42:53 +0000
commit74e8ed4bde37a3ce42579e4601e0a54120853c89 (patch)
treeca0c74f490498124d784d8f2c2ed4c146d10097f /manifest_xml.py
parent2fe84e17b923f29139dc6056756ab30078864c18 (diff)
downloadgit-repo-74e8ed4bde37a3ce42579e4601e0a54120853c89.tar.gz
Expose upstream and dest-branch attributes through environment
Recent changes in ChromeOS Infra to ensure we're reading from snapshot manifests properly have exposed several bugs in our assumptions about manifest files. Mainly that the revision field for a project does _not_ have to refer to a ref, it can just be a commit hash. Several places assume that the revision field can be parsed as a ref to get the branch the project is on, which isn't true. To fix this we need to be able to look at the upstream and dest-branch attributes of the repo, so we expose them through the environment variables set in `repo forall`. Test: manual 'repo forall' run Bug: https://crbug.com/1032441 Change-Id: I2c039e0f4b2e0f430602932e91b782edb6f9b1ed Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/263132 Reviewed-by: Mike Frysinger <vapier@google.com> Tested-by: Sean McAllister <smcallis@google.com>
Diffstat (limited to 'manifest_xml.py')
0 files changed, 0 insertions, 0 deletions