Building within Github Actions always results in snapshot

[alibabashack]

Issue

version: 1.8.0 (from maven central)

usage context:

• [x] maven command line: 3.8.? (Github actions default) and 3.6.3 (Ubuntu 20.04)
• [x] eclipse: none
• [x] netbeans: none
• [x] Intellij IDEA: none
• [x] NO config file (defaults apply - > maven versionig scheme)
• [x] checkout is performed with tag fetch, so all tags and branches are available to jgitver

Problem description:

When building from an annotated git tag (detached head) within github actions CI, this always results in a - SNAPSHOT suffix version for me. The version number is picked up correctly from the tag. However, I expect a release version without SNAPSHOT.

For example see the following actions run: https://github.com/alibabashack/rxtx/runs/4606812319?check_suite_focus=true

In bullet

• run actions/checkout@v2
  • fetching the repository: Note all tags and branches are fetched and are visible (especially tag 2.4)
  • checking out the ref: Note tag 2.4 is checked out in detached head state
• Bundle rxtx Java native libs: 2.4.0-SNAPSHOT is calculated from the tag.
• Release: Note version 2.4.0-SNAPSHOT is created from tag 2.4.

I expect version 2.4.0 instead of 2.4.0-SNAPSHOT.

When the version is calculated based on the same repository on my local ubuntu 20.04 machine (also in detached head state on the same tag) no SNAPSHOT suffix is added.

I do not see any configuration differences between the github action run and my local run. Still it results in two different outcomes. Any ideas?

Thanks a lot for this project. It is a huge help in order to DRY in the insane maven world.

[alibabashack]

I think I accidentally did not use an annotated tag. I will inveatigate first.

[alibabashack]

Ok, I really used an annotated tag. I was confused by the git options, but option -m implies -a, so this does not seem to be the issue here.

[alibabashack]

I found the problem: A misconfiguration of my github workflow. If your workflow is distributed across multiple build host, all of them have to checkout the repository with a fetch-depth of 0, of course. :)

[McFoggy]

Fine that you found your issue. It's the same with other CI (Jenkins for example) if you build on different nodes you have to checkout on all of them.