Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
Jenkins 1.605
Ubuntu 14.04 within a docker container
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
- is duplicated by
-
JENKINS-28260 Java String Index Out of Range
-
- Closed
-
-
JENKINS-28291 Git creates malformed changelog.xml files
-
- Closed
-
scaytrase 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.