[JIRA] [hp-application-automation-tools-plugin] (JENKINS-19516) having problem to connect the QC
ily naf commented on JENKINS-19516 having problem to connect the QC Me too with ALM 11.0 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] [plugin] (JENKINS-20864) Unknown Naginator Icon next to Failed Build
ily naf commented on JENKINS-20864 Unknown Naginator Icon next to Failed Build Didn't happen on v1.535 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] [plugin] (JENKINS-20864) Unknown Naginator Icon next to Failed Build
ily naf created JENKINS-20864 Unknown Naginator Icon next to Failed Build Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: undisplayed_naginator_icon.png Components: plugin Created: 04/Dec/13 3:26 AM Description: Some icon can't be displayed next to a failed build (scheduled by Naginator). Please see the screenshot. URL to icon image looks like this http://host:port/plugin/naginator/redo.png Environment: RHEL 5.7 64 bit + JDK 1.7.0_25 64bit + JBoss AS 7.1.1 Final Project: Jenkins Priority: Minor Reporter: ily naf 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] [subversion] (JENKINS-16343) Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error.
ily naf commented on JENKINS-16343 Access to the Subversion repository doesnt work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error. They could be related because we also apply the workaround "-Dsvnkit.http.sslProtocols=SSLv3" here. 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] [subversion] (JENKINS-16343) Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error.
ily naf commented on JENKINS-16343 Access to the Subversion repository doesnt work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error. Happens here with Jenkins 1.514, Subversion plugin 1.45, Subversion server 1.6.5 (https + SSLv3). Doesn't happen with SVN server 1.5.5 (https + TLSv1) on the same Jenkins + Subversion plugin. This is quite annoying the workaround requires manipulation on all nodes (master, slaves). Please consider a fix for this roadblock ASAP. Tks! 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] [subversion] (JENKINS-16343) Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error.
ily naf edited a comment on JENKINS-16343 Access to the Subversion repository doesnt work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error. Happens here with Jenkins 1.514, Subversion plugin 1.45, Subversion server 1.6.5 (https + SSLv3). Also happen with SVN server 1.5.5 (https + TLSv1) on the same Jenkins + Subversion plugin. This is quite annoying the workaround requires manipulation on all nodes (master, slaves). Please consider a fix for this roadblock ASAP. Tks! 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] [subversion] (JENKINS-16343) Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error.
ily naf edited a comment on JENKINS-16343 Access to the Subversion repository doesnt work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error. Happens here with Jenkins 1.514, Subversion plugin 1.45, Subversion server 1.6.5 (https + SSLv3). Also happens with SVN server 1.5.5 (https + TLSv1) on the same Jenkins + Subversion plugin. This is quite annoying the workaround requires manipulation on all nodes (master, slaves). Please consider a fix for this roadblock ASAP. Tks! 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] [subversion] (JENKINS-16343) Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error.
ily naf edited a comment on JENKINS-16343 Access to the Subversion repository doesnt work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error. Happens here with Jenkins 1.514, Subversion plugin 1.45, Subversion server 1.6.5 (https + SSLv3). Doesn't happen with SVN server 1.5.5 (https + TLSv1) on the same Jenkins + Subversion plugin. This is quite annoying the workaround requires manipulation on all nodes (master, slaves). Please consider a fix for this roadblock ASAP. Tks! 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] (JENKINS-2351) Moving Hudson to new server out of sync error
ily naf commented on JENKINS-2351 Moving Hudson to new server out of sync error The same problem here. Once a commit is made during the time when SVN server is out of sync (let's say one month ahead the current time), there is no way for you to have the job check out the latest rev again(it's always stuck at some rev ahead of that "guilty" commit). Although I've tried to clean up the working copy check out again. The only workaround is added @HEAD to the repo URL. This is really frustrating 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.
