Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-28134

Git clone fails since git client plugin 1.17.0

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: git-client-plugin
    • Labels:
      None
    • Environment:
      Jenkins 1.605
      Ubuntu 14.04 within a docker container
    • Similar Issues:

      Description

      When updating from 1.16.1 to 1.17.0 I suddenly get the following exception when cloning a workspace:

      Cloning the remote Git repository
      remote: Counting objects
      remote: Compressing objects
      Receiving objects
      Resolving deltas
      Updating references
      Checking out Revision 991f2e24d0b9b02801369a4a1297d08b2b923ef8 (origin/master)
      FATAL: String index out of range: -1
      java.lang.StringIndexOutOfBoundsException: String index out of range: -1
      	at java.lang.String.substring(String.java:1955)
      	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 hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:906)
      	at hudson.model.AbstractBuild.access$600(AbstractBuild.java:107)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:621)
      	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531)
      	at hudson.model.Run.execute(Run.java:1751)
      	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      	at hudson.model.ResourceController.execute(ResourceController.java:89)
      	at hudson.model.Executor.run(Executor.java:240)
      

        Attachments

          Issue Links

            Activity

            cbeikov Christian Beikov created issue -
            Hide
            scaytrase Pavel Batanov added a comment -

            Experiencing he same issue at 2 of each 3 builds. Either at start of the build or at the end of it. Or both, like this:

            Checking out Revision 6ff2ffa2f43ae955014c560633d8ce01bc65bcb9 (refs/remotes/origin/production)
            FATAL: String index out of range: -1
            java.lang.StringIndexOutOfBoundsException: String index out of range: -1
            	at java.lang.String.substring(String.java:1911)
            	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 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.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
            	at hudson.model.ResourceController.execute(ResourceController.java:98)
            	at hudson.model.Executor.run(Executor.java:374)
            Build did not succeed and the project is configured to only push after a successful build, so no pushing will occur.
            Successfully triggered JIRA to update builds of this job
            Notified Stash for commit with id 6ff2ffa2f43ae955014c560633d8ce01bc65bcb9
            FATAL: String index out of range: -1
            java.lang.StringIndexOutOfBoundsException: String index out of range: -1
            	at java.lang.String.substring(String.java:1911)
            	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 hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:909)
            	at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:877)
            	at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:352)
            	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:675)
            	at hudson.model.Run.execute(Run.java:1769)
            	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
            	at hudson.model.ResourceController.execute(ResourceController.java:98)
            	at hudson.model.Executor.run(Executor.java:374)
            
            Show
            scaytrase Pavel Batanov added a comment - Experiencing he same issue at 2 of each 3 builds. Either at start of the build or at the end of it. Or both, like this: Checking out Revision 6ff2ffa2f43ae955014c560633d8ce01bc65bcb9 (refs/remotes/origin/production) FATAL: String index out of range: -1 java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang. String .substring( String .java:1911) 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 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.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Build did not succeed and the project is configured to only push after a successful build, so no pushing will occur. Successfully triggered JIRA to update builds of this job Notified Stash for commit with id 6ff2ffa2f43ae955014c560633d8ce01bc65bcb9 FATAL: String index out of range: -1 java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang. String .substring( String .java:1911) 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 hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:909) at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:877) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:352) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:675) at hudson.model.Run.execute(Run.java:1769) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374)
            Hide
            rogeriocolferai Rogério Colferai added a comment - - edited

            We had same issue. Either at the start of build or at the end of it, like this :

            Jenkins version: LTS 1.596.1

            07:28:17 + git push -f origin jenkins/master-aux:jenkins/master-aux
            07:28:21 remote:
            07:28:21 remote:
            remote: Processing changes: closed: 1, refs: 1
            remote: Processing changes: closed: 1, refs: 1
            remote: Processing changes: closed: 1, refs: 1
            remote: Processing changes: closed: 1, refs: 1, done
            07:28:21 To https://ipadmin@gerrit.cpqd.com.br/dsso/cdk
            07:28:21 4949602..52d0260 jenkins/master-aux -> jenkins/master-aux
            07:28:21 FATAL: String index out of range: -1
            07:28:21 java.lang.StringIndexOutOfBoundsException: String index out of range: -1
            07:28:21 at java.lang.String.substring(String.java:1911)
            07:28:21 at hudson.plugins.git.GitChangeSet.isoDateFormat(GitChangeSet.java:179)
            07:28:21 at hudson.plugins.git.GitChangeSet.parseCommit(GitChangeSet.java:118)
            07:28:21 at hudson.plugins.git.GitChangeSet.<init>(GitChangeSet.java:89)
            07:28:21 at hudson.plugins.git.GitChangeLogParser.parseCommit(GitChangeLogParser.java:73)
            07:28:21 at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:67)
            07:28:21 at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:44)
            07:28:21 at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:25)
            07:28:21 at hudson.scm.ChangeLogParser.parse(ChangeLogParser.java:57)
            07:28:21 at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:894)
            07:28:21 at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:862)
            07:28:21 at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:349)
            07:28:21 at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:346)
            07:28:21 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:687)
            07:28:21 at hudson.model.Run.execute(Run.java:1784)
            07:28:21 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
            07:28:21 at hudson.model.ResourceController.execute(ResourceController.java:89)
            07:28:21 at hudson.model.Executor.run(Executor.java:240)

            Show
            rogeriocolferai Rogério Colferai added a comment - - edited We had same issue. Either at the start of build or at the end of it, like this : Jenkins version: LTS 1.596.1 07:28:17 + git push -f origin jenkins/master-aux:jenkins/master-aux 07:28:21 remote: 07:28:21 remote: remote: Processing changes: closed: 1, refs: 1 remote: Processing changes: closed: 1, refs: 1 remote: Processing changes: closed: 1, refs: 1 remote: Processing changes: closed: 1, refs: 1, done 07:28:21 To https://ipadmin@gerrit.cpqd.com.br/dsso/cdk 07:28:21 4949602..52d0260 jenkins/master-aux -> jenkins/master-aux 07:28:21 FATAL: String index out of range: -1 07:28:21 java.lang.StringIndexOutOfBoundsException: String index out of range: -1 07:28:21 at java.lang.String.substring(String.java:1911) 07:28:21 at hudson.plugins.git.GitChangeSet.isoDateFormat(GitChangeSet.java:179) 07:28:21 at hudson.plugins.git.GitChangeSet.parseCommit(GitChangeSet.java:118) 07:28:21 at hudson.plugins.git.GitChangeSet.<init>(GitChangeSet.java:89) 07:28:21 at hudson.plugins.git.GitChangeLogParser.parseCommit(GitChangeLogParser.java:73) 07:28:21 at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:67) 07:28:21 at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:44) 07:28:21 at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:25) 07:28:21 at hudson.scm.ChangeLogParser.parse(ChangeLogParser.java:57) 07:28:21 at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:894) 07:28:21 at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:862) 07:28:21 at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:349) 07:28:21 at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:346) 07:28:21 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:687) 07:28:21 at hudson.model.Run.execute(Run.java:1784) 07:28:21 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 07:28:21 at hudson.model.ResourceController.execute(ResourceController.java:89) 07:28:21 at hudson.model.Executor.run(Executor.java:240)
            Hide
            markewaite Mark Waite added a comment -

            Ouch. Sorry about that. What version of the git plugin are you running with the git client plugin?

            Does the problem resolve itself if you revert from 1.17.0 to 1.16.1 (and restart the Jenkins server)? I assume it will be resolved by that revert, since there was a specific fix included in 1.17.0 for date format parsing in change sets.

            Show
            markewaite Mark Waite added a comment - Ouch. Sorry about that. What version of the git plugin are you running with the git client plugin? Does the problem resolve itself if you revert from 1.17.0 to 1.16.1 (and restart the Jenkins server)? I assume it will be resolved by that revert, since there was a specific fix included in 1.17.0 for date format parsing in change sets.
            Hide
            markewaite Mark Waite added a comment -

            Looking at the code, I think the change in git client plugin 1.17.0 needs a corresponding change in the git plugin to no longer rely on an git changeset format from the prior plugin. I'll need to check with Nicolas De Loof to see if there are other techniques we can consider to not break the previous version of the git plugin, while still including his fix to date parsing in a changeset.

            Show
            markewaite Mark Waite added a comment - Looking at the code, I think the change in git client plugin 1.17.0 needs a corresponding change in the git plugin to no longer rely on an git changeset format from the prior plugin. I'll need to check with Nicolas De Loof to see if there are other techniques we can consider to not break the previous version of the git plugin, while still including his fix to date parsing in a changeset.
            markewaite Mark Waite made changes -
            Field Original Value New Value
            Summary Git clone fails since 1.17.0 Git clone fails since git client plugin 1.17.0
            Hide
            scaytrase Pavel Batanov added a comment -

            Mark, reverting helps. So this can be workarounded

            Show
            scaytrase Pavel Batanov added a comment - Mark, reverting helps. So this can be workarounded
            Hide
            markewaite Mark Waite added a comment -

            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.

            Show
            markewaite Mark Waite added a comment - 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.
            Hide
            scaytrase Pavel Batanov added a comment -

            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.

            Show
            scaytrase Pavel Batanov added a comment - 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.
            Hide
            kriskra Kristian Kraljic added a comment - - edited

            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 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.getChangeSet(AbstractBuild.java:877)
            	at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:352)
            	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:675)
            	at hudson.model.Run.execute(Run.java:1769)
            	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
            	at hudson.model.ResourceController.execute(ResourceController.java:98)
            	at hudson.model.Executor.run(Executor.java:374)
            Finished: FAILURE
            
            Show
            kriskra Kristian Kraljic added a comment - - edited 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 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.getChangeSet(AbstractBuild.java:877) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:352) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:675) at hudson.model.Run.execute(Run.java:1769) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Finished: FAILURE
            kriskra Kristian Kraljic made changes -
            Priority Minor [ 4 ] Major [ 3 ]
            Hide
            scaytrase Pavel Batanov added a comment -

            Kristian, have you restarted jenkins after reverting the plugin?

            Show
            scaytrase Pavel Batanov added a comment - Kristian, have you restarted jenkins after reverting the plugin?
            Hide
            markewaite Mark Waite added a comment -

            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.

            Show
            markewaite Mark Waite added a comment - 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.
            Hide
            kriskra Kristian Kraljic added a comment -

            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.

            Show
            kriskra Kristian Kraljic added a comment - 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.
            kriskra Kristian Kraljic made changes -
            Priority Major [ 3 ] Minor [ 4 ]
            Hide
            ntshako Hannes Kogler added a comment -

            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.

            Show
            ntshako Hannes Kogler added a comment - 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.
            Hide
            markewaite Mark Waite added a comment -

            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.

            Show
            markewaite Mark Waite added a comment - 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.
            Hide
            scaytrase Pavel Batanov added a comment -

            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.

            Show
            scaytrase Pavel Batanov added a comment - 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.
            Hide
            markewaite Mark Waite added a comment -

            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.

            Show
            markewaite Mark Waite added a comment - 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.
            Hide
            scaytrase Pavel Batanov added a comment -

            Mark, looks working with 1.17.0 and snapshot. I'll write here if I get something broken unexpectedly.

            Show
            scaytrase Pavel Batanov added a comment - Mark, looks working with 1.17.0 and snapshot. I'll write here if I get something broken unexpectedly.
            markewaite Mark Waite made changes -
            Link This issue is duplicated by JENKINS-28260 [ JENKINS-28260 ]
            Hide
            markewaite Mark Waite added a comment -

            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.

            Show
            markewaite Mark Waite added a comment - 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.
            markewaite Mark Waite made changes -
            Link This issue is duplicated by JENKINS-28291 [ JENKINS-28291 ]
            Hide
            markewaite Mark Waite added a comment -

            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.

            Show
            markewaite Mark Waite added a comment - 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.
            Hide
            markewaite Mark Waite added a comment -

            Fix included in git plugin 2.4.0 released 18 July 2015

            Show
            markewaite Mark Waite added a comment - Fix included in git plugin 2.4.0 released 18 July 2015
            markewaite Mark Waite made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            markewaite Mark Waite made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 162848 ] JNJira + In-Review [ 208718 ]

              People

              • Assignee:
                ndeloof Nicolas De Loof
                Reporter:
                cbeikov Christian Beikov
              • Votes:
                8 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: