• Type: Improvement
• Resolution: Unresolved
• Priority: Minor
• Component/s: parameterized-remote-trigger-plugin
• Labels:

  • plugin
• Environment:

  All

[JENKINS-29219] Log and output error messages during address validation

Steve Ramage created issue - 2015-07-03 18:25

Collapse comment: Saurya SS added a comment - 2015-12-03 02:09, Edited by Saurya SS - 2015-12-03 02:10

Saurya SS added a comment - 2015-12-03 02:09 - edited

I am not able to get parameterized remote trigger plugin work with Jenkins 1.584. I get the same error message "Address looks good, but we were not able to connect to it". I need to use https url instead of http. As soon as I enter http url it says "Address looks good" message and I am able to trigger build but not successful due to following errors.

Unexpected end of file from server
Connection to remote server failed, waiting for to retry - 10 seconds until next attempt.
Retry attempt #1 out of 5
Unexpected end of file from server
Connection to remote server failed, waiting for to retry - 10 seconds until next attempt.
Retry attempt #2 out of 5

I am not able to trigger jobs remotely. It seems https url is not acceptable in plugin configuration.

Please advise.

Expand comment: Saurya SS added a comment - 2015-12-03 02:09, Edited by Saurya SS - 2015-12-03 02:10

Saurya SS added a comment - 2015-12-03 02:09 - edited I am not able to get parameterized remote trigger plugin work with Jenkins 1.584. I get the same error message "Address looks good, but we were not able to connect to it". I need to use https url instead of http. As soon as I enter http url it says "Address looks good" message and I am able to trigger build but not successful due to following errors. Unexpected end of file from server Connection to remote server failed, waiting for to retry - 10 seconds until next attempt. Retry attempt #1 out of 5 Unexpected end of file from server Connection to remote server failed, waiting for to retry - 10 seconds until next attempt. Retry attempt #2 out of 5 I am not able to trigger jobs remotely. It seems https url is not acceptable in plugin configuration. Please advise.

Collapse comment: Steve Ramage added a comment - 2015-12-03 15:38

Steve Ramage added a comment - 2015-12-03 15:38

Hi saurya1979,

I worked on a similar problem several months ago when I filed the bug. I also filed a patch and a pull request, but I think the maintainer is gone. The pull request is here: https://github.com/SJrX/parameterized-remote-trigger-plugin/commit/acf24b131e94a01c184bf5dcf840c6dac9137e4c
. If I had to venture a guess, it is that you have a self signed certificate (or a certificate signed by a CA that isn't standard), and Java is tossing an exception.

Steve Ramage

Expand comment: Steve Ramage added a comment - 2015-12-03 15:38

Steve Ramage added a comment - 2015-12-03 15:38 Hi saurya1979 , I worked on a similar problem several months ago when I filed the bug. I also filed a patch and a pull request, but I think the maintainer is gone. The pull request is here: https://github.com/SJrX/parameterized-remote-trigger-plugin/commit/acf24b131e94a01c184bf5dcf840c6dac9137e4c . If I had to venture a guess, it is that you have a self signed certificate (or a certificate signed by a CA that isn't standard), and Java is tossing an exception. Steve Ramage

R. Tyler Croy made changes - 2016-07-25 23:51

Workflow

Original: JNJira [ 164088 ]

New: JNJira + In-Review [ 181504 ]