Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Build fails with 'Error: Failed to parse git describe output: "v0.1.0a-26-g6817b33'
See original GitHub issueBug description
When using a tag that does not 100% respect a classic semver version, unity-builder fails with the following error message:
Error: Failed to parse git describe output: "v0.1.0a-26-g6817b33
How to reproduce
- Use unity-actions@v1.4
- push a commit and a tag like
v0.1.0ato trigger the pipeline
It should build, but it fails.
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (10 by maintainers)
Top Results From Across the Web
git describe fails with "fatal: No names found ... - Stack Overflow
The solution was to ensure that the initial clone of the repo in the build environment was not a shallow clone (i.e. the...
Read more >Unexpected `git describe` result in detached CI logs ... - GitLab
This bug happens on an omnibus instance. See details below. Results of GitLab environment info. Expand for output related to GitLab environment ...
Read more >Build identification as a string inside code with Git Describe
The above steps will replace any pre-processor define FWCODEREV in your code,with a quoted string containing the output of the shell command Git...
Read more >[SOLVED] Travis CI builds failed - dev - Hugo Discourse
make test govendor test +local ? github.com/spf13/hugo [no test files] ok ... 0.019s --- FAIL: TestReleaseNotesWriter (0.02s) Error Trace: ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Creating a tag on your main branch
v2.1should fix your problem as per https://github.com/game-ci/unity-builder/issues/163#issuecomment-723582126.I think I also reproduced this problem with tags that looked like this in the repository: