Details
-
Type:
Bug
-
Status: Reopened (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: git-parameter-plugin
-
Labels:
-
Environment:master: Ubuntu 14.04, Agents: Ubuntu 14.04, CentOS 7.5, SLES-12SP2
Jenkins 2.128, git-parameter 0.9.2
-
Similar Issues:
Description
Occasionally not getting a list of tags for build with parameters.
The jenkins.log has this message:
WARNING: [ project-release ] Download tags from the repository failed
hudson.plugins.git.GitException: Command "git ls-remote -t ssh://gerrit.example.com:29418/group/project v18.*" returned status code 128:
stdout:
stderr: /bin/bash: line 0: exec: nc: not found
ssh_exchange_identification: Connection closed by remote host
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists
.
On the CentOS 7.5 system, nc is at /usr/bin.
nc --help
Ncat 7.50 ( https://nmap.org/ncat )
On the other systems, nc is at /bin and nc reports:
nc -h OpenBSD netcat (Debian patchlevel 1.105-7ubuntu1) This is nc from the netcat-openbsd package. An alternative nc is available in the netcat-traditional package.
jemalmbe@coral-sles12-1:~> nc -h OpenBSD netcat (SUSE Linux) This is nc from the netcat-openbsd package. An alternative nc is available in the netcat-traditional package.
The access to the git repository is through ssh and the git repository is working.
If I configure a default tag value in the git parameter, that is used for building.
But when this happens, I have no way to automatically build the top tag sorted from the list by default.
Attachments
Issue Links
- duplicates
-
-
- Resolved
-
- relates to
-
-
- Resolved
-
Activity
Changing the repository entry to have the ssh credentials with it did not change the behavior.
John Malmberg
added a comment - Changing the repository entry to have the ssh credentials with it did not change the behavior. Hi,
I released plugin in version 0.9.11 where this issue was resolved, could you check that and confirm the issue is resolved
Regards
Boguslaw
Still not working.
Only change is now nothing is logged to the /var/log/jenkins/log on failure.
Did you try reproducing this by temporarily moving where the nc command is located on the build agent?
That is what I see different on the for the distros where it works and does not work, and that also goes along with the original bug report.
John Malmberg
added a comment - Still not working.
Only change is now nothing is logged to the /var/log/jenkins/log on failure.
Did you try reproducing this by temporarily moving where the nc command is located on the build agent?
That is what I see different on the for the distros where it works and does not work, and that also goes along with the original bug report. Still not working.
John Malmberg
added a comment - Still not working. 
Except for the error message, the behavior seems to be the same. It is only working if the build agent is running CentOS,
It is not working if the build agent is running Ubuntu 14.04, or SLES 12SP2.