[JIRA] [publish-over-ssh-plugin] (JENKINS-30964) Upgrade to 1.633 blocks Configure
Title: Message Title Dmitry Esarev commented on JENKINS-30964 Re: Upgrade to 1.633 blocks Configure seems like a dup of JENKINS-30922 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [mantis] (JENKINS-16840) Unable to connect to Mantis
Dmitry Zanozin commented on JENKINS-16840 Unable to connect to Mantis The similar problem for me. I'm trying to use server named "mantis" in local network. Can't retrieve projects and categories. log contains: ... Jan 29, 2014 3:15:08 PM hudson.plugins.mantis.soap.mantis120.MantisSessionImpl INFO: Mantis version is 1.2.X Jan 29, 2014 3:15:09 PM hudson.plugins.mantis.MantisSite isConnect WARNING: Failed to connect http://mantis/ (cause: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.). ... Mantis 1.2.11 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-15718) Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...)
Dmitry Gil commented on JENKINS-15718 Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...) The same issue with Jenkins 1.489 and TFS 1.20 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