[JIRA] [ec2] (JENKINS-19943) EC2 plugin cannot connect to slaves outside us-east-1 on new AWS accounts (using EC2-VPC)
Michael Tutty commented on JENKINS-19943 EC2 plugin cannot connect to slaves outside us-east-1 on new AWS accounts (using EC2-VPC) This is a blocker for me, using a non-EC2 Jenkins server. +1 for the fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Michael Tutty commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails Juergen, that is the same behavior I saw as well. It didn't matter whether I had a credential, added one or removed one, it always failed the same way. Your question about further debugging info is exactly why I suggested better logging in this section. There isn't anything I could find to gather more data at runtime. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Michael Tutty commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails It's not self-signed certs in my case. Something is wrong with either the default credentials added to the GitClient instance, or the format of the command that's actually run. No network request is ever opened from the Jenkins server, it fails immediately. Notice line 150 in the Git plugin's job configuration code: https://github.com/jenkinsci/git-plugin/blame/master/src/main/java/hudson/plugins/git/UserRemoteConfig.java - it was changed on 10-09-13. Also check line 1261 in the Git client implementation: https://github.com/jenkinsci/git-client-plugin/blame/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java - credential-related changes also made about a month ago. This would be a great place to add some logging code, I was unable to diagnose anything with the logging facility in Jenkins web UI. Specifically, it would be great when the underlying process returns != 0, to know the exact command-line and args that were used, as well as the contents of STDOUT and STDERR. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Michael Tutty commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails I downgraded git-client and git packages in Jenkins, and it's working again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
