Error while pushing a tag since Gitlab

[GBeauny]

Hello,

I got an error through my jenkins build while pushing a tag since Jenkins, have you an idea why?

Here my output :

git rev-parse origin/refs/tags/v0.0.1^{commit} # timeout=10 FATAL: Command "git rev-parse origin/refs/tags/v0.0.1^{commit}" returned status code 128: stdout: origin/refs/tags/v0.0.1^{commit}

stderr: fatal: ambiguous argument 'origin/refs/tags/v0.0.1^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions

hudson.plugins.git.GitException: Command "git rev-parse origin/refs/tags/v0.0.1^{commit}" returned status code 128: stdout: origin/refs/tags/v0.0.1^{commit}

stderr: fatal: ambiguous argument 'origin/refs/tags/v0.0.1^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions

Plugin version i'm using: 1.2.2 Jenkins version: 1.610 Git version: 1.7.10.4

Thanks guys.

[GBeauny]

Nobody there?

[timols]

Hi @GBeauny4D what values did you set for the git configuration in jenkins?

[GBeauny]

Hello Timols, sorry for late answers,

My values are the following ones :

First repo :

• Repository URL : My git url
• My credential
• Advanced : Name : origin, Refspec : +refs/heads/:refs/remotes/origin/ +refs/pull/:refs/remotes/origin/pr/

Second repo :

• Repository URL : ${gitlabSourceRepoURL}
• Name : ${gitlabSourceRepoName}
• Refspec : empty
• Branches to build : ${gitlabSourceRepoName}/${gitlabSourceBranch}
• Gitlabversion : 7.0

Additional behaviours :

• Merge before build :

Name of repository : origin -branch to merge to : ${gitlabTargetBranch} -Merge strategy : default -Fast-forward mode : --ff

Thank you,

[timols]

Ok, this seems to be an underlying git plugin issue. What version of the git plugin are you using?

[GBeauny]

Git plugin jenkins : last version : 2.4.0. thanks.

[GBeauny]

I had to open an issue on Jenkins Jira but didn't help : https://issues.jenkins-ci.org/browse/JENKINS-29718. Please, could you try on your side to confirm the issue? Thanks in advance.

[timols]

Unfortunately @GBeauny I have no particular access to the maintainers of the git plugin. Looks like you were given some suggestions in the issue you opened on how to resolve