tree 92412c08e68e595f6f80a7bae764a9a1998de407
parent fb1f2fb8201f81c20115c917ddb91207db1afb91
author Ivan Frade <ifrade@google.com> 1643760320 -0800
committer Ivan Frade <ifrade@google.com> 1649093922 +0000

RepoUpdater: store in destination the source manifest revision

Right now it is not possible to know the specific revision of a manifest
that defined the destination repository. This is problematic for
debugging and to detect mismatches e.g. when the manifest is updated but
the translation to superproject failed.

Write to the destination repository a ".supermanifest" file with the
repo, reference and commit-id of the source manifest used.

Alternatives considered to write the source repo/ref/hash:

  * .gitattributes of the .gitmodules file. Some updates in the manifest
    don't touch the .gitmodules (e.g. a linkfile change), so it can fall
    out of sync.

  * commit message. Caller would need to follow the commit history to
    find the latest modification by repo command. This is not helpful
    e.g. for build bots that want to get the value in one call.

This requires the RepoCommand#addToDestination method introduced in JGit
6.1

Change-Id: Iad66199d40828143f4764421247714b6f0625233