CODEWITHSUNDEEP
gitjgit
Leon Radley
Leon Radley

Reputation: 7682

Get submodule hash from bare repository

We have a gitolite server with our customers custom apps.

Every app has a submodule "repository/core" which refers to our base app.

We would now like to create a dashboard which shows all our customers apps and at which revision there core is at.

gitolite stores everything in bare repositories on disk and the dashboard app has direct access to the repos / or using ssh keys if that's easier.

My question is how would I from a bare repository find out what revision a submodule is at, and who committed it?

Upvotes: 5

Views: 1018

Answers (3)

Rüdiger Herrmann
Rüdiger Herrmann

Reputation: 21025

JGit has a SubmoduleStatusCommand that lists all known submodules. Note that this command works only on non-bare repositories.

Git git = Git.open( new File( "/path/to/repo/.git" ) );
Map<String,SubmoduleStatus> submodules = git.submoduleStatus().call();
SubmoduleStatus status = submodules.get( "repository/core" );
ObjectId headId = status.getHeadId();

As you can see, the command returns a map of submodules-names along with their respective SubmoduleStatus which includes the SHA-1 of the HEAD commit.

There is also an article about JGit's submodule API that I wrote some time ago that has some more details.

For a bare repository you would have to read the the submodule's HEAD ID directly from the repository's object database like so:

try( RevWalk revWalk = new RevWalk( repository ) ) {
  RevCommit headCommit = revWalk.parseCommit( repository.resolve( Constants.HEAD ) );
}
try( TreeWalk treeWalk = TreeWalk.forPath( repository, "repository/core", headCommit.getTree() ) ) {
  ObjectId blobId = treeWalk.getObjectId( 0 );
  ObjectLoader objectLoader = repository.open( blobId, Constants.OBJ_BLOB );
  try( InputStream inputStream = objectLoader.openStream() ) {
    // read contents from the input stream
  }
}

Upvotes: 2

pwaller
pwaller

Reputation: 641

I just had to implement this for a CI server. The tricky part is remaining with a bare checkout.

My solution was as follows:

1) git show HEAD:.gitmodules can be used to get a list of paths which are submodules.

2) for each path =, the third field of this can be used to determine the SHA the submodule is at:

git ls-tree -z -d HEAD -- <submodule path>

Upvotes: 6

AlBlue
AlBlue

Reputation: 24060

You can list the .gitmodules to find out which paths are deemed to be modules, and then go through them and find out what the <module>.git/HEAD/ reference is pointing to (probably a symbolic reference, like ref: refs/heads/master, which you'd then have to chain to find the value of refs/heads/master). That will then give you the most recent commit hash of that module.

Upvotes: 2

Related Questions