[
https://issues.apache.org/jira/browse/SCM-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962275#comment-17962275
]
ASF GitHub Bot commented on SCM-624:
------------------------------------
jira-importer opened a new issue, #832:
URL: https://github.com/apache/maven-scm/issues/832
**[Kristian
Rosenvold](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=krosenvold)**
opened
**[SCM-624](https://issues.apache.org/jira/browse/SCM-624?redirect=false)** and
commented
Atlassian Bamboo does a quationable check-out using jgit that leaves a lot
of changes appearing on "git show", which subsequently confuses the parsing.
Changing the command to use "git rev-parse --verify HEAD^{commit}" will always
output just the sha1, reducing any chance of confusion in the parsing.
---
No further details from
[SCM-624](https://issues.apache.org/jira/browse/SCM-624?redirect=false)
> Revision number parsing can fail with lots of unstaged changes
> --------------------------------------------------------------
>
> Key: SCM-624
> URL: https://issues.apache.org/jira/browse/SCM-624
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Reporter: Kristian Rosenvold
> Assignee: Kristian Rosenvold
> Priority: Major
> Fix For: 1.6
>
>
> Atlassian Bamboo does a quationable check-out using jgit that leaves a lot of
> changes appearing on "git show", which subsequently confuses the parsing.
> Changing the command to use "git rev-parse --verify HEAD^{commit}" will
> always output just the sha1, reducing any chance of confusion in the parsing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
