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

NullPointerException after Update to 1.11 of plugin

    Details

    • Similar Issues:

      Description

      We have updated the plugin from 1.10 to 1.11. After that builds using it fail with a NullPointerException:

      java.lang.NullPointerException
      at hudson.plugins.testng.Publisher.perform(Publisher.java:186)
      at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)

      Solution is probably to also consider the new field unstableFails in Publisher.readResolve().

        Attachments

          Issue Links

            Activity

            Hide
            splendid Stefan Gärtner added a comment -

            Great, thanks for the quick response!

            Show
            splendid Stefan Gärtner added a comment - Great, thanks for the quick response!
            Hide
            nullin Nalin Makar added a comment -

            fixed in 1.12

            Show
            nullin Nalin Makar added a comment - fixed in 1.12
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: nullin
            Path:
            README
            src/main/java/hudson/plugins/testng/Publisher.java
            http://jenkins-ci.org/commit/testng-plugin-plugin/50160c41b947b81812189a5197da427893e23273
            Log:
            Fixed: JENKINS-34711 - NullPointerException after Update to 1.11 of plugin

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: nullin Path: README src/main/java/hudson/plugins/testng/Publisher.java http://jenkins-ci.org/commit/testng-plugin-plugin/50160c41b947b81812189a5197da427893e23273 Log: Fixed: JENKINS-34711 - NullPointerException after Update to 1.11 of plugin
            Hide
            splendid Stefan Gärtner added a comment -

            Excerpt from config.xml

            <hudson.plugins.testng.Publisher plugin="testng-plugin@1.10">
            <reportFilenamePattern>UI/Test/Reports/*/.xml</reportFilenamePattern>
            <escapeTestDescp>true</escapeTestDescp>
            <escapeExceptionMsg>true</escapeExceptionMsg>
            <showFailedBuilds>false</showFailedBuilds>
            <unstableOnSkippedTests>false</unstableOnSkippedTests>
            <failureOnFailedTestConfig>false</failureOnFailedTestConfig>
            </hudson.plugins.testng.Publisher>

            Show
            splendid Stefan Gärtner added a comment - Excerpt from config.xml <hudson.plugins.testng.Publisher plugin="testng-plugin@1.10"> <reportFilenamePattern>UI/Test/Reports/* / .xml</reportFilenamePattern> <escapeTestDescp>true</escapeTestDescp> <escapeExceptionMsg>true</escapeExceptionMsg> <showFailedBuilds>false</showFailedBuilds> <unstableOnSkippedTests>false</unstableOnSkippedTests> <failureOnFailedTestConfig>false</failureOnFailedTestConfig> </hudson.plugins.testng.Publisher>
            Hide
            stupchiy Sergiy Tupchiy added a comment - - edited

            Can confirm the same, even after upgrade from 1.09 to 1.10
            Jenkins ver.: 1.656
            OS: Ubuntu 13.10

            Seems after upgrade and first run of the jobs, config's are not updated, as supposed, with newer version tag:

            Noticed with "Job Config History" plugin, tag <hudson.plugins.testng.Publisher plugin="testng-plugin@1.10"> left the same, but for other plugin's got updated after first run.

            After re-save config, solves the problem

            Show
            stupchiy Sergiy Tupchiy added a comment - - edited Can confirm the same, even after upgrade from 1.09 to 1.10 Jenkins ver.: 1.656 OS: Ubuntu 13.10 Seems after upgrade and first run of the jobs, config's are not updated, as supposed, with newer version tag: Noticed with "Job Config History" plugin, tag <hudson.plugins.testng.Publisher plugin="testng-plugin@1.10"> left the same, but for other plugin's got updated after first run. After re-save config, solves the problem
            Hide
            splendid Stefan Gärtner added a comment -

            Yes, just running the build again, no special steps. Maybe some config files could help?

            Sorry, we have already downgraded the plugin to 1.10 as the build was urgent.
            With the old version the build was successful.

            Show
            splendid Stefan Gärtner added a comment - Yes, just running the build again, no special steps. Maybe some config files could help? Sorry, we have already downgraded the plugin to 1.10 as the build was urgent. With the old version the build was successful.
            Hide
            nullin Nalin Makar added a comment -

            As a workaround, can you open config for the job, save without changing anything and then kick off the job again?

            Show
            nullin Nalin Makar added a comment - As a workaround, can you open config for the job, save without changing anything and then kick off the job again?
            Hide
            nullin Nalin Makar added a comment -

            I'll look into this ASAP. What steps did you follow to reproduce this issue? Kick off a job without opening the configuration for the job?

            Show
            nullin Nalin Makar added a comment - I'll look into this ASAP. What steps did you follow to reproduce this issue? Kick off a job without opening the configuration for the job?

              People

              • Assignee:
                nullin Nalin Makar
                Reporter:
                splendid Stefan Gärtner
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: