Inconsistent error when two prefixed and annotated tags point to the same commit

[jfleck1]

Setup:
Gradle with Kotlin DSL and multiple subprojects, each with independent versioning

Symptom:
When running a build, either in the command line or within IntelliJ, this error occurs:

Inconsistent git describe: native was library@0.0.14-3-g05e75f8 and jgit was 05e75f8.

This occurred when a single commit addresses issues in multiple gradle subprojects within the same git repository. This causes prefixed release tags for each subproject to be added to the same commit.

After stepping through the code, I found that the RefWithTagNameComparator wasn't comparing the tags correctly.

gradle-git-version/src/main/java/com/palantir/gradle/gitversion/RefWithTagNameComparator.java

Line 46 in c62bf60

public int compare(RefWithTagName tag1, RefWithTagName tag2) {

The comparator then causes the incorrect ref to be added, or none at all, when trying to use updateCommitHashMap.

gradle-git-version/src/main/java/com/palantir/gradle/gitversion/JGitDescribe.java

Line 122 in 8b81ba6

private static void updateCommitHashMap(

Because updateCommitHashMap fails to add the commit to the map, commitHashToTag doesn't contain the correct tag.

gradle-git-version/src/main/java/com/palantir/gradle/gitversion/JGitDescribe.java

Line 53 in 8b81ba6

Map<String, RefWithTagName> commitHashToTag = mapCommitsToTags(git);

Solution Idea
Possibly refactor how the commit hash to tag loading works so that the full tag name is used instead. Because multiple tags can point to the same commit hash, it makes sense to use the full /ref/tags listing since that is the unique listing.

Workaround:
Avoid releasing and adding two tags to the same commit. In a multiple project structure, this makes sense... in a way. One subproject's fixes and commits should be independent of the other subproject's. Write more succinct and focused commits, one per subproject.

[apanloco]

I had this error and just tested the new 3.0.0 release, and can confirm that this issue is actually fixed now!