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

java.lang.RuntimeException: No author in changeset null

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • git-plugin

    Description

      I have set-up a build with the git plugin - it uses polling, but it always fails with the following error seen in "Git Polling Log":

      Git Polling Log

      Started on Feb 10, 2013 12:06:00 PM
      Using strategy: Default
      [poll] Last Build : #2
      Fetching changes from the remote Git repositories
      Fetching upstream changes from git://devel.brailcom.org/git/lcg.git
      Polling for changes in
      Seen branch in repository origin/HEAD
      Seen branch in repository origin/eurochance
      Seen branch in repository origin/master
      Seen branch in repository origin/parse-inline-markup
      ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@6099210f[LCG]
      java.lang.RuntimeException: No author in changeset null
      at hudson.plugins.git.GitChangeSet.getAuthorName(GitChangeSet.java:324)
      at hudson.plugins.git.GitSCM.isRevExcluded(GitSCM.java:1788)
      at hudson.plugins.git.GitSCM.access$300(GitSCM.java:72)
      at hudson.plugins.git.GitSCM$1.invoke(GitSCM.java:755)
      at hudson.plugins.git.GitSCM$1.invoke(GitSCM.java:731)
      at hudson.FilePath.act(FilePath.java:865)
      at hudson.FilePath.act(FilePath.java:838)
      at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:731)
      at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:644)
      at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
      at hudson.scm.SCM.poll(SCM.java:373)
      at hudson.model.AbstractProject._poll(AbstractProject.java:1480)
      at hudson.model.AbstractProject.poll(AbstractProject.java:1410)
      at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439)
      at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468)
      at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
      at java.util.concurrent.FutureTask.run(FutureTask.java:166)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
      at java.lang.Thread.run(Thread.java:636)

      Attachments

        Issue Links

          Activity

            Code changed in jenkins
            User: Mark Waite
            Path:
            src/main/java/hudson/plugins/git/GitChangeSet.java
            src/test/java/hudson/plugins/git/GitChangeSetEmptyTest.java
            src/test/java/hudson/plugins/git/GitChangeSetEuroTest.java
            src/test/java/hudson/plugins/git/GitChangeSetSimpleTest.java
            src/test/java/hudson/plugins/git/GitChangeSetTest.java
            http://jenkins-ci.org/commit/git-plugin/287e5434d790c9a1c7204e38a09cb843b209a3d7
            Log:
            [Fix JENKINS-16737] and [Fix JENKINS-10434] - no exception if author not found

            Return unknown user rather than throwing exception in GitChangeSet

            Refer to JENKINS-16737 and JENKINS-10434 for two cases where a
            GitChangeSet cannot find an author and throws a RuntimeException when
            it would be much better to report an unknown user and allow execution
            to continue.

            Added a Polish character to the accented character test

            Use more diacritics in the latin accented character test

            Use parameterized GitChangeSet test to better cover cases

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Mark Waite Path: src/main/java/hudson/plugins/git/GitChangeSet.java src/test/java/hudson/plugins/git/GitChangeSetEmptyTest.java src/test/java/hudson/plugins/git/GitChangeSetEuroTest.java src/test/java/hudson/plugins/git/GitChangeSetSimpleTest.java src/test/java/hudson/plugins/git/GitChangeSetTest.java http://jenkins-ci.org/commit/git-plugin/287e5434d790c9a1c7204e38a09cb843b209a3d7 Log: [Fix JENKINS-16737] and [Fix JENKINS-10434] - no exception if author not found Return unknown user rather than throwing exception in GitChangeSet Refer to JENKINS-16737 and JENKINS-10434 for two cases where a GitChangeSet cannot find an author and throws a RuntimeException when it would be much better to report an unknown user and allow execution to continue. Added a Polish character to the accented character test Use more diacritics in the latin accented character test Use parameterized GitChangeSet test to better cover cases

            Code changed in jenkins
            User: Mark Waite
            Path:
            src/main/java/hudson/plugins/git/GitChangeSet.java
            src/test/java/hudson/plugins/git/GitChangeSetEmptyTest.java
            src/test/java/hudson/plugins/git/GitChangeSetEuroTest.java
            src/test/java/hudson/plugins/git/GitChangeSetSimpleTest.java
            src/test/java/hudson/plugins/git/GitChangeSetTest.java
            http://jenkins-ci.org/commit/git-plugin/cb6f13a3e3158332f76a45e853b3766fe83d5828
            Log:
            [Fix JENKINS-16737] and [Fix JENKINS-10434] - no exception if author not found

            Return unknown user rather than throwing exception in GitChangeSet

            Refer to JENKINS-16737 and JENKINS-10434 for two cases where a
            GitChangeSet cannot find an author and throws a RuntimeException when
            it would be much better to report an unknown user and allow execution
            to continue.

            Added a Polish character to the accented character test

            Use more diacritics in the latin accented character test

            Use parameterized GitChangeSet test to better cover cases

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Mark Waite Path: src/main/java/hudson/plugins/git/GitChangeSet.java src/test/java/hudson/plugins/git/GitChangeSetEmptyTest.java src/test/java/hudson/plugins/git/GitChangeSetEuroTest.java src/test/java/hudson/plugins/git/GitChangeSetSimpleTest.java src/test/java/hudson/plugins/git/GitChangeSetTest.java http://jenkins-ci.org/commit/git-plugin/cb6f13a3e3158332f76a45e853b3766fe83d5828 Log: [Fix JENKINS-16737] and [Fix JENKINS-10434] - no exception if author not found Return unknown user rather than throwing exception in GitChangeSet Refer to JENKINS-16737 and JENKINS-10434 for two cases where a GitChangeSet cannot find an author and throws a RuntimeException when it would be much better to report an unknown user and allow execution to continue. Added a Polish character to the accented character test Use more diacritics in the latin accented character test Use parameterized GitChangeSet test to better cover cases
            markewaite Mark Waite added a comment -

            Fix should be in git plugin 2.2.8, preventing the plugin from throwing an exception even if it finds a case where the changeset author is null. It will return an unknown user rather than throwing an exception.

            Unfortunately, because I can't duplicate the problem, I can't be 100% confident that will resolve the problem entirely, but I am reasonably confident that getAuthorName will no longer throw a RuntimeException.

            markewaite Mark Waite added a comment - Fix should be in git plugin 2.2.8, preventing the plugin from throwing an exception even if it finds a case where the changeset author is null. It will return an unknown user rather than throwing an exception. Unfortunately, because I can't duplicate the problem, I can't be 100% confident that will resolve the problem entirely, but I am reasonably confident that getAuthorName will no longer throw a RuntimeException.
            danielbeck Daniel Beck added a comment -

            According to JENKINS-25132, ci.jenkins-ci.org has that problem. So it may be possible to determine whether the fix works by upgrading Git plugin there.

            danielbeck Daniel Beck added a comment - According to JENKINS-25132 , ci.jenkins-ci.org has that problem. So it may be possible to determine whether the fix works by upgrading Git plugin there.
            markewaite Mark Waite added a comment -

            Fix released in git plugin 2.3 10 Nov 2014

            markewaite Mark Waite added a comment - Fix released in git plugin 2.3 10 Nov 2014

            People

              maxvohlken Max Vohlken
              dusek Boris DuĊĦek
              Votes:
              11 Vote for this issue
              Watchers:
              23 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: