versionname started to include very long sha hash about gradle-android-git-version HOT 5 CLOSED

also i think your readme has an error because the default format seems to misspell where the percentage symbol is placed, see above where i just copied it from your readme.

from gradle-android-git-version.

Was this performed on a commit from a detached head? It looks like git is giving the full sha1 instead of a branch name because there is no branch.

The string looks a bit strange because the - character is inside the delimiters. This is actually intentional so that the each part (including the - character) disappears when not needed.

from gradle-android-git-version.

i don't think so, but actually there is something interesting if i look at the commit from which it was build:

I guess you are right, i can test tomorrow if the format looks fine if it was builded from a regular commit. in this case it was build from a remote merge.

regarding the default format string, got it. understand it now.

from gradle-android-git-version.

Let me know -- many CI systems optimize or otherwise manipulate their local git repo so that it doesn't look like what you might get on your local system and this is a common source of problems for any git-based auto-versioning code. You'll need an "unshallow" fetch on a normal branch for all of this to work.

from gradle-android-git-version.

ok a regular build went through bamboo and yes, it was actually because of the remote merge it seems. maybe that is something which can be added to the readme, but at least we now know why it happens.

from gradle-android-git-version.