[JENKINS-20167] Unable to commit release version on Git master branch from Artifactory Release Staging

We are unable to commit a release on our git repository by using the Jenkins artifactory plugin - Release Management.

We were previously using the artifactory release staging link to build and commit our release on git.

If we try to commit the release from the Jenkins slave, we got the following exception :

[RELEASE] Committing release version on branch ''

[RELEASE] Creating tag 'project-1.0.4'

[RELEASE] Pushing branch '' to 'git@​gitlab.domain.com:project-group/project.git'

Failure in post build SCM action: remote file operation failed: /jenkins/workspace/build-project at hudson.remoting.Channel@​3a2b6ce6:build-01

So, we tried to commit from the master node:

[RELEASE] Committing release version on branch ''

[RELEASE] Creating tag 'project-1.0.4'

[RELEASE] Pushing branch '' to 'git@​gitlab.domain.com:project-group/project.git'

Failure in post build SCM action: Failed to push: Command "push git@​gitlab.domain.com:project-group/project.git refs/heads/" returned status code 128:

stdout:

stderr: fatal: remote part of refspec is not a valid name in refs/heads/

Seems that the plugin can't commit to the master branch (why an empty branch?).

You can find an attached image for the artifactory release staging configuration.

---
Originally reported by alapenna, imported from: Unable to commit release version on Git master branch from Artifactory Release Staging

• status: Open
  
• priority: Major
  
• component(s): artifactory-plugin, git-plugin, release-plugin
  
• label(s): artifactory, branch, jenkins, plugin, release, tag
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 3
  
• imported: 2025-12-02
  

We are unable to commit a release on our git repository by using the Jenkins artifactory plugin - Release Management.


We were previously using the artifactory release staging link to build and commit our release on git.


If we try to commit the release from the Jenkins slave, we got the following exception :




[RELEASE] Committing release version on branch ''

[RELEASE] Creating tag 'project-1.0.4'

[RELEASE] Pushing branch '' to 'git@gitlab.domain.com:project-group/project.git'

Failure in post build SCM action: remote file operation failed: /jenkins/workspace/build-project at hudson.remoting.Channel@3a2b6ce6:build-01


So, we tried to commit from the master node:




[RELEASE] Committing release version on branch ''

[RELEASE] Creating tag 'project-1.0.4'

[RELEASE] Pushing branch '' to 'git@gitlab.domain.com:project-group/project.git'

Failure in post build SCM action: Failed to push: Command "push git@gitlab.domain.com:project-group/project.git refs/heads/" returned status code 128:

stdout: 

stderr: fatal: remote part of refspec is not a valid name in refs/heads/


Seems that the plugin can't commit to the master branch (why an empty branch?).


You can find an attached image for the artifactory release staging configuration.

• environment: Ubuntu 12.04, Jenkins 1.536, Jenkins Artifactory Plugin 2.2.0

- [artifactory_release_staging.png](https://raw.githubusercontent.com/jenkinsci/attachments-from-jira-issues-last/refs/heads/main/attachments/24554/artifactory_release_staging.png)
>