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

After upgrade to 2.73.3: java.lang.NumberFormatException: For input string: "GIT_"

    XMLWordPrintable

Details

    Description

      We upgraded from 2.73.2 to 2.73.3 and get now following error message:

       

      java.lang.NumberFormatException: For input string: "GIT_"
          at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
          at java.lang.Integer.parseInt(Integer.java:580)
          at jenkins.model.IdStrategy$CaseInsensitive.idFromFilename(IdStrategy.java:306)
          at hudson.model.User$AllUsers.scanAll(User.java:1056)
      Caused: java.lang.reflect.InvocationTargetException
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
          at java.lang.reflect.Method.invoke(Method.java:498)
          at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104)
      Caused: java.lang.Error
          at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110)
          at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175)
          at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
          at jenkins.model.Jenkins$7.runTask(Jenkins.java:1090)
          at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
          at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
          at java.lang.Thread.run(Thread.java:745)
      Caused: org.jvnet.hudson.reactor.ReactorException
          at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269)
          at jenkins.InitReactorRunner.run(InitReactorRunner.java:47)
          at jenkins.model.Jenkins.executeReactor(Jenkins.java:1124)
          at jenkins.model.Jenkins.<init>(Jenkins.java:929)
          at hudson.model.Hudson.<init>(Hudson.java:86)
          at hudson.model.Hudson.<init>(Hudson.java:82)
          at hudson.WebAppMain$3.run(WebAppMain.java:235)
      Caused: hudson.util.HudsonFailedToLoad
          at hudson.WebAppMain$3.run(WebAppMain.java:252)

      Attachments

        Issue Links

          Activity

            Version of git plugin is 3.6.4, but I don't know if it is the plugin which results into this error. Maybe it is a jenkins core issue as the problem starts with upgrading to jenkins 2.73.3. Switching back to 2.73.2 resolves this problem.

            opi Alexander Opitz added a comment - Version of git plugin is 3.6.4, but I don't know if it is the plugin which results into this error. Maybe it is a jenkins core issue as the problem starts with upgrading to jenkins 2.73.3. Switching back to 2.73.2 resolves this problem.
            markewaite Mark Waite added a comment -

            A change was made in Jenkins 2.73.3 to store certain dangerous user names on the disc in a different format. Could you check the "users" directory in your JENKINS_HOME to see if there is a directory there with GIT_ as the initial substring?

            markewaite Mark Waite added a comment - A change was made in Jenkins 2.73.3 to store certain dangerous user names on the disc in a different format. Could you check the "users" directory in your JENKINS_HOME to see if there is a directory there with GIT_ as the initial substring?

            Yes, seams so but don't know why they exist.

            jenkins@jenkins:~/users$ ls -l
            insgesamt 128
            ...
            drwxr-xr-x 2 jenkins nogroup 4096 Okt 11 12:26 $git_author_email
            drwxr-xr-x 2 jenkins nogroup 4096 Aug 14 2013 $GIT_AUTHOR_EMAIL
            ...

            opi Alexander Opitz added a comment - Yes, seams so but don't know why they exist. jenkins@jenkins:~/users$ ls -l insgesamt 128 ... drwxr-xr-x 2 jenkins nogroup 4096 Okt 11 12:26 $git_author_email drwxr-xr-x 2 jenkins nogroup 4096 Aug 14 2013 $GIT_AUTHOR_EMAIL ...
            markewaite Mark Waite added a comment -

            opi you can delete those two problem user directories without any significant risk.

            I suspect they were created because there is a commit in one of your git repositories that has those strings as the text of the commit message. The git plugin defaults to creating users in Jenkins for names that are detected in commits, even if those user names are not real users of Jenkins.

            markewaite Mark Waite added a comment - opi you can delete those two problem user directories without any significant risk. I suspect they were created because there is a commit in one of your git repositories that has those strings as the text of the commit message. The git plugin defaults to creating users in Jenkins for names that are detected in commits, even if those user names are not real users of Jenkins.

            Ok, understand ... that could be as in some projects the first commits are done with such commits.

            So, will there be a fix or do I need to take care somewhere?

            opi Alexander Opitz added a comment - Ok, understand ... that could be as in some projects the first commits are done with such commits. So, will there be a fix or do I need to take care somewhere?
            markewaite Mark Waite added a comment -

            opi I'm reasonably confident there will be a fix, but I'm not sure of the timing of the fix. Removing those directories seems like an easy alternative, rather than waiting for the development and testing of a fix.

            markewaite Mark Waite added a comment - opi I'm reasonably confident there will be a fix, but I'm not sure of the timing of the fix. Removing those directories seems like an easy alternative, rather than waiting for the development and testing of a fix.

            People

              Unassigned Unassigned
              opi Alexander Opitz
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: