| commit | 1c927d3ff894654b8bb13991f13ee202f7b7d377 | [log] [tgz] |
|---|---|---|
| author | Ivan Frade <ifrade@google.com> | Tue Feb 01 16:05:20 2022 -0800 |
| committer | Ivan Frade <ifrade@google.com> | Mon Apr 04 17:38:42 2022 +0000 |
| tree | 92412c08e68e595f6f80a7bae764a9a1998de407 | |
| parent | fb1f2fb8201f81c20115c917ddb91207db1afb91 [diff] |
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
The plugin will update a superproject to contain the submodules defined in the manifest XML file whenever the manifest repo is changed.
For more information see the documentation or the build instructions