[JIRA] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-28134 Git clone fails since git client plugin 1.17.0 Change By: Mark Waite Status: Resolved Closed 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] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Title: Message Title Mark Waite resolved as Fixed Fix included in git plugin 2.4.0 released 18 July 2015 Jenkins / JENKINS-28134 Git clone fails since git client plugin 1.17.0 Change By: Mark Waite Status: Open Resolved Resolution: Fixed 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] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Title: Message Title Mark Waite commented on JENKINS-28134 Re: Git clone fails since git client plugin 1.17.0 The git client plugin 1.17.1 released 8 May 2015 using the code from git client plugin 1.16.1. That hides the git plugin bug which caused this bug and others. Once a simultaneous release of git plugin (master branch) and git client plugin (master branch) can be confirmed that they are reliable, this bug will be resolved. Until then, it is hidden from view, but not resolved. 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] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Title: Message Title Hannes Kogler commented on JENKINS-28134 Re: Git clone fails since git client plugin 1.17.0 Hi! same problem here. a workaround as I see it is an alternative solution to a real and clean solution, but after all it should be some kind of solution. To be forced to manually cleanup the workspace and start a build again, when this error occurs is no solution at all (just manual extra work) and therefore it cannot be a real workaround. So I don't really agree with you to treat this ticket with such a low priority... imagine a system with about hundreds of build jobs, where this error occurs e.g. only one time per day for every single build job in a Continous Integration environment. I think this error is able to create very much manual effort and therefore costs after all. 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] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Title: Message Title Mark Waite commented on JENKINS-28134 Re: Git clone fails since git client plugin 1.17.0 Hannes Kogler I sincerely regret that I did not detect the ISO date parsing problem in git plugin 2.3.5 which was exposed by git client plugin 1.17.0. Unfortunately, I was running an unreleased version of the git plugin on the systems where I performed my tests. I'll be more thorough prior to future releases. I agree with you that it is a serious problem to tell users that they need to downgrade their plugin. I'm not sure any workspace cleanup is required, but at least one user has reported that it was required for him. Did downgrading the plugin work for you (without cleaning the workspace)? The most direct path to resolve the problem is to release a new version of the git plugin, a version which already contains the fix for the problem exposed by git client plugin 1.17.0. That means the new version of the git plugin needs more testing, lest recent changes to it cause more problems for the 50,000+ installations of the plugin. I've posted a pre-release version of the git plugin 2.3.6. I'd love to hear your feedback to confirm that it resolves this issue and does not introduce other, more serious issues. I'm running that build on my test machine currently. 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] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Title: Message Title Pavel Batanov commented on JENKINS-28134 Re: Git clone fails since git client plugin 1.17.0 Do I have to try this snapshot plugin with latest Git client plugin? Or stay on 1.16.1? With 1.16.1 it works well. 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] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Title: Message Title Mark Waite commented on JENKINS-28134 Re: Git clone fails since git client plugin 1.17.0 I just had to revert the 2.3.6 snapshot build from my production system with git client plugin 1.17.0 due to non-stop builds. The build runs even though no change should have been detected. More investigation will be needed. 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] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Title: Message Title Mark Waite commented on JENKINS-28134 Re: Git clone fails since git client plugin 1.17.0 Pavel Batanov either is fine, since it needs to operate correctly with both 1.16.1 and 1.17.0. I'm currently running the pre-release with git client plugin 1.17.0 in my home instance in in my production Jenkins at work. If you're running with 1.16.1, that increases our chances of detecting problems related to version interactions. Since the bug was only exposed with git client plugin 1.17.0, you should not see the problem in your configuration. The goal of your testing is to confirm that other things are not broken unexpectedly in the git plugin 2.3.6 release. 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] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Title: Message Title Pavel Batanov commented on JENKINS-28134 Re: Git clone fails since git client plugin 1.17.0 Mark, looks working with 1.17.0 and snapshot. I'll write here if I get something broken unexpectedly. 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] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Kristian Kraljic updated JENKINS-28134 Git clone fails since git client plugin 1.17.0 Cleaning workspace and second restart after reverting to 1.16.1 helped to solve the issue. As a working work arround is available, reverted ticket priority to Minor. Thanks a lot. Change By: Kristian Kraljic (02/May/15 2:26 PM) Priority: Major Minor 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/d/optout.
[JIRA] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Kristian Kraljic updated JENKINS-28134 Git clone fails since git client plugin 1.17.0 Same issue for me on 1.17.0. Reverting to 1.16.1 didn't solve the issue either in my case, therefore raising the priority of the ticket ot Major. Checking out Revision 488bf9f13a0eee7ed8999a9015c92ec81a7b9000 (refs/remotes/master) FATAL: String index out of range: -1 java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1995) at hudson.plugins.git.GitChangeSet.isoDateFormat(GitChangeSet.java:179) at hudson.plugins.git.GitChangeSet.parseCommit(GitChangeSet.java:118) at hudson.plugins.git.GitChangeSet.init(GitChangeSet.java:89) at hudson.plugins.git.GitChangeLogParser.parseCommit(GitChangeLogParser.java:73) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:67) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:44) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:25) at hudson.scm.ChangeLogParser.parse(ChangeLogParser.java:57) at org.jenkinsci.plugins.multiplescms.MultiSCMChangeLogParser$LogSplitter.endElement(MultiSCMChangeLogParser.java:99) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:606) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1741) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2898) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:844) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1210) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:568) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:302) at javax.xml.parsers.SAXParser.parse(SAXParser.java:328) at org.jenkinsci.plugins.multiplescms.MultiSCMChangeLogParser.parse(MultiSCMChangeLogParser.java:135) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:909) at hudson.model.AbstractBuild.access$600(AbstractBuild.java:107) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1744) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) FATAL: String index out of range: -1 java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1995) at hudson.plugins.git.GitChangeSet.isoDateFormat(GitChangeSet.java:179) at hudson.plugins.git.GitChangeSet.parseCommit(GitChangeSet.java:118) at hudson.plugins.git.GitChangeSet.init(GitChangeSet.java:89) at hudson.plugins.git.GitChangeLogParser.parseCommit(GitChangeLogParser.java:73) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:67) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:44) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:25) at hudson.scm.ChangeLogParser.parse(ChangeLogParser.java:57) at org.jenkinsci.plugins.multiplescms.MultiSCMChangeLogParser$LogSplitter.endElement(MultiSCMChangeLogParser.java:99) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:606) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1741) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2898) at
[JIRA] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Mark Waite commented on JENKINS-28134 Git clone fails since git client plugin 1.17.0 Kristian Kraljic did you restart Jenkins after you reverted from 1.17.0 to 1.16.1? The 1.16.1 code definitely does not include the ISO date format parsing change, so if you are truly running 1.16.1 and seeing that message, then there is some other problem. 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/d/optout.
[JIRA] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Pavel Batanov commented on JENKINS-28134 Git clone fails since git client plugin 1.17.0 Kristian, have you restarted jenkins after reverting the plugin? 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/d/optout.
[JIRA] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Kristian Kraljic edited a comment on JENKINS-28134 Git clone fails since git client plugin 1.17.0 Same issue for me on 1.17.0. Reverting to 1.16.1 didn't solve the issue either in my case, therefore raising the priority of the ticket to Major. Checking out Revision 488bf9f13a0eee7ed8999a9015c92ec81a7b9000 (refs/remotes/master) FATAL: String index out of range: -1 java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1995) at hudson.plugins.git.GitChangeSet.isoDateFormat(GitChangeSet.java:179) at hudson.plugins.git.GitChangeSet.parseCommit(GitChangeSet.java:118) at hudson.plugins.git.GitChangeSet.init(GitChangeSet.java:89) at hudson.plugins.git.GitChangeLogParser.parseCommit(GitChangeLogParser.java:73) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:67) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:44) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:25) at hudson.scm.ChangeLogParser.parse(ChangeLogParser.java:57) at org.jenkinsci.plugins.multiplescms.MultiSCMChangeLogParser$LogSplitter.endElement(MultiSCMChangeLogParser.java:99) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:606) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1741) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2898) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:844) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1210) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:568) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:302) at javax.xml.parsers.SAXParser.parse(SAXParser.java:328) at org.jenkinsci.plugins.multiplescms.MultiSCMChangeLogParser.parse(MultiSCMChangeLogParser.java:135) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:909) at hudson.model.AbstractBuild.access$600(AbstractBuild.java:107) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1744) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) FATAL: String index out of range: -1 java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1995) at hudson.plugins.git.GitChangeSet.isoDateFormat(GitChangeSet.java:179) at hudson.plugins.git.GitChangeSet.parseCommit(GitChangeSet.java:118) at hudson.plugins.git.GitChangeSet.init(GitChangeSet.java:89) at hudson.plugins.git.GitChangeLogParser.parseCommit(GitChangeLogParser.java:73) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:67) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:44) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:25) at hudson.scm.ChangeLogParser.parse(ChangeLogParser.java:57) at org.jenkinsci.plugins.multiplescms.MultiSCMChangeLogParser$LogSplitter.endElement(MultiSCMChangeLogParser.java:99) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:606) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1741) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2898) at
[JIRA] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Mark Waite commented on JENKINS-28134 Git clone fails since git client plugin 1.17.0 Thanks, Pavel Batanov, that means we can probably live with this problem for a few days while a new release of the git plugin is prepared. Nicolas De Loof has been using pre-release versions of the git plugin with several other users so now it just needs a careful review of the changes since last release and some detailed testing before it is released generally. Would you be willing to assist with testing a pre-release of the next version of the git plugin? If so, I could give you a link to a version you could upload to your Jenkins server. 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/d/optout.
[JIRA] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Pavel Batanov commented on JENKINS-28134 Git clone fails since git client plugin 1.17.0 Since it stands revertable and my jenkins is not mission critical - I can spend some time on testing, so feel free to provide me a link and a bit of instructions if more than just run my jobs is needed. 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/d/optout.
[JIRA] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Pavel Batanov commented on JENKINS-28134 Git clone fails since git client plugin 1.17.0 Mark, reverting helps. So this can be workarounded 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/d/optout.
[JIRA] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0
Mark Waite updated JENKINS-28134 Git clone fails since git client plugin 1.17.0 Change By: Mark Waite (29/Apr/15 4:31 PM) Summary: Gitclonefailssince gitclientplugin 1.17.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/d/optout.
