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

Java String Index Out of Range

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: git-plugin
    • Labels:
      None
    • Environment:
      Jenkins 1.612, Ubuntu Server 14.04
    • Similar Issues:

      Description

      I have a project that is configured to git fetch from Atlassian Stash repository. It then runs buildr to compile it. There are many times that the whole process fails with the following:

      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:57)
      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:894)
      at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:862)
      at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:349)
      at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:346)
      at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:687)
      at hudson.model.Run.execute(Run.java:1743)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:89)
      at hudson.model.Executor.run(Executor.java:240)

      Sometimes the process fails immediately after it checks out the revision. Other times, it will finish completely but then display this output at the end and 'fail' even though it completed.

        Attachments

          Issue Links

            Activity

            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
            danielbeck Daniel Beck added a comment -

            Mark Waite Should this be resolved as duplicate?

            Show
            danielbeck Daniel Beck added a comment - Mark Waite Should this be resolved as duplicate?
            Hide
            markewaite Mark Waite added a comment -

            Daniel Beck it is definitely a duplicate and the duplicate is linked in the bug report. Is the general bug reporting workflow that duplicates are resolved, even when the bug which they duplicate is not yet resolved?

            I've been assuming (without any basis in anything I read) that duplicate bugs stayed open until the bug they duplicate was resolved. If that's not the case,then there may be several git and git client bugs which should be resolved as duplicates.

            Is there a general page which I should be reading about the bug workflow and bug handling policies? I'd like to be consistent with the rest of the community, or at least with the "standard way" of doing things if there is a standard way.

            Show
            markewaite Mark Waite added a comment - Daniel Beck it is definitely a duplicate and the duplicate is linked in the bug report. Is the general bug reporting workflow that duplicates are resolved, even when the bug which they duplicate is not yet resolved? I've been assuming (without any basis in anything I read) that duplicate bugs stayed open until the bug they duplicate was resolved. If that's not the case,then there may be several git and git client bugs which should be resolved as duplicates. Is there a general page which I should be reading about the bug workflow and bug handling policies? I'd like to be consistent with the rest of the community, or at least with the "standard way" of doing things if there is a standard way.
            Hide
            danielbeck Daniel Beck added a comment -

            Mark Waite We only have the wiki page on issue tracking, but it's mostly descriptive based on what I've seen in the past. In core, we usually resolve duplicate issues using the Resolution Duplicate by convention/habit. I think one of the advantages is that all further actions/comments/votes/watches can be centralized that way.

            Show
            danielbeck Daniel Beck added a comment - Mark Waite We only have the wiki page on issue tracking , but it's mostly descriptive based on what I've seen in the past. In core, we usually resolve duplicate issues using the Resolution Duplicate by convention/habit. I think one of the advantages is that all further actions/comments/votes/watches can be centralized that way.
            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

              People

              • Assignee:
                ndeloof Nicolas De Loof
                Reporter:
                jagwirez Taylor K
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: