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

Details

Type: Bug
Status: Open (View Workflow)
Priority: Major
Resolution: Unresolved
Component/s: artifactory-plugin, git-plugin, release-plugin
Labels:
- artifactory
- branch
- jenkins
- plugin
- release
- tag
Environment:
Ubuntu 12.04, Jenkins 1.536, Jenkins Artifactory Plugin 2.2.0

Similar Issues:

Show

Description

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.

Hide

Permalink

Bob Tiernay added a comment - 2013-12-05 00:13 - edited

I'm getting something similar, but I'm not sure it is related:

[RELEASE] Committing release version on branch 'release/dcc-2.1.9'
[RELEASE] Creating tag '2.1.9'
[RELEASE] Pushing branch 'release/dcc-2.1.9' to 'https://github.com/icgc-dcc/dcc'
Failure in post build SCM action: Failed to push: Command "push https://github.com/icgc-dcc/dcc refs/heads/release/dcc-2.1.9" returned status code 128:
stdout: 
stderr: error: cannot run /bin/echo : No such file or directory

/bin/echo does indeed exist and is executable by the jenkins user.

This started to happen recently after upgrading Jenkins from 1.540 to 1.541 and upgrading some plugins related to git, etc. I have a suspicion that the Artifactory plugin isn't playing well with other plugins after the upgrade. Using Artifactory plugin 2.2.1

Show

Bob Tiernay added a comment - 2013-12-05 00:13 - edited I'm getting something similar, but I'm not sure it is related: [RELEASE] Committing release version on branch 'release/dcc-2.1.9' [RELEASE] Creating tag '2.1.9' [RELEASE] Pushing branch 'release/dcc-2.1.9' to 'https://github.com/icgc-dcc/dcc' Failure in post build SCM action: Failed to push: Command "push https://github.com/icgc-dcc/dcc refs/heads/release/dcc-2.1.9" returned status code 128: stdout: stderr: error: cannot run /bin/echo : No such file or directory /bin/echo does indeed exist and is executable by the jenkins user. This started to happen recently after upgrading Jenkins from 1.540 to 1.541 and upgrading some plugins related to git, etc. I have a suspicion that the Artifactory plugin isn't playing well with other plugins after the upgrade. Using Artifactory plugin 2.2.1

Hide

Permalink

Nicolas De Loof added a comment - 2013-10-22 13:39

pushing branch syntax should indeed be :
push origin (local branch refsepc):(remote branch refspec)

looks like artifactory plugin is missusing git-client API

Show

Nicolas De Loof added a comment - 2013-10-22 13:39 pushing branch syntax should indeed be : push origin (local branch refsepc):(remote branch refspec) looks like artifactory plugin is missusing git-client API

Jenkins

Unable to commit release version on Git master branch from Artifactory Release Staging

Details

Description

Attachments

Attachments

Activity

People

Dates