[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title John Malmberg reopened an issue Still not working. Jenkins / JENKINS-52051 git-parameter exec: nc: not found. Change By: John Malmberg Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191646.1529444715000.11458.1563208080196%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title John Malmberg commented on JENKINS-52051 Re: git-parameter exec: nc: not found. 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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191646.1529444715000.11456.1563208020143%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title Boguslaw Klimas resolved as Fixed 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 Jenkins / JENKINS-52051 git-parameter exec: nc: not found. Change By: Boguslaw Klimas Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191646.1529444715000.2832.1560886620293%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title John Malmberg commented on JENKINS-52051 Re: git-parameter exec: nc: not found. Changing the repository entry to have the ssh credentials with it did not change the behavior. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title John Malmberg commented on JENKINS-52051 Re: git-parameter exec: nc: not found. 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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title
John Malmberg edited a comment on JENKINS-52051
Re: git-parameter exec: nc: not found.
It is still failing to find the releases when using Ubuntu or SLESS/(Open SUSE Leap) build agents.It is generating a different message in the log.{code}WARNING: [ argobots-release ] Download tags from the repository failedhudson.plugins.git.GitException: Command "git ls-remote -t ssh://review. hpdd example . intel. com:29418/daos/argobots v1" returned status code 128:stdout:stderr: Permission denied (publickey).fatal: Could not read from remote repository.{code}The repository is access via a SSH-AGENT supplied credentials.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title
John Malmberg edited a comment on JENKINS-52051
Re: git-parameter exec: nc: not found.
It is still failing to find the releases when using Ubuntu or SLESS/(Open SUSE Leap) build agents.It looks like it is still coded to use generating a different message in the log.{code}WARNING: [ argobots-release ] Download tags from the repository failedhudson.plugins.git.GitException: Command "git ls-remote -t ssh: / usr / bin review.hpdd.intel.com:29418 / nc instead of checking to see where the nc program really daos/argobots v1" returned status code 128:stdout:stderr: Permission denied (publickey).fatal: Could not read from remote repository.{code}The repository is access via a SSH-AGENT supplied credentials .
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title John Malmberg reopened an issue Jenkins / JENKINS-52051 git-parameter exec: nc: not found. Change By: John Malmberg Resolution: Cannot Reproduce Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title John Malmberg commented on JENKINS-52051 Re: git-parameter exec: nc: not found. It is still failing to find the releases when using Ubuntu or SLESS/(Open SUSE Leap) build agents. It looks like it is still coded to use /usr/bin/nc instead of checking to see where the nc program really is. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title John Malmberg commented on JENKINS-52051 Re: git-parameter exec: nc: not found. I will try to verify this week. The issue appears to be that the code was looking only for "/usr/bin/nc", and on the systems where the plugin was failing for me, the path needed is "/bin/nc". So it should have been easy to reproduce by temporary moving nc to /bin/nc on a test system. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title Boguslaw Klimas resolved as Cannot Reproduce Release 0.9.10 Jenkins / JENKINS-52051 git-parameter exec: nc: not found. Change By: Boguslaw Klimas Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title Boguslaw Klimas commented on JENKINS-52051 Re: git-parameter exec: nc: not found. Hi, I can't reproduce this issue, but I found code smells, which can provide to unexpected behavior. commit: f85678c3 I changed it in release 0.9.10. Additional I changed error handling, please look on wiki page If this issue steal occurred in your environment after update the plugin. Please add more information which I can use to reproduce this issue and reopen this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
