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

Build-failure-analyzer afected by JEP-200 in Jenkins 2.102

XMLWordPrintable

       

      Since latest update I get lots of:

       

      ConversionException: Refusing to unmarshal foundFailureCauses for security reasons; see https://jenkins.io/redirect/class-filter/ ---- Debugging information ---- class : java.util.Collections$SynchronizedRandomAccessList required-type : java.util.Collections$SynchronizedRandomAccessList converter-type : hudson.util.XStream2$BlacklistedTypesConverter path : /flow-build/actions/com.sonyericsson.jenkins.plugins.bfa.model.FailureCauseBuildAction/foundFailureCauses line number : 321 -------------------------------

       

      I have followed instruction prodided in the link found above:

      If you find such a case, please report it in the Jenkins issue tracker, under the appropriate plugin component. Link it to JENKINS-47736 and add the JEP-200 label. If at all possible, include complete steps to reproduce the problem from scratch. Jenkins developers will strive to evaluate the reason for the violation and offer a fix in the form of a core and/or plugin update. For more details and current status, see Plugins affected by fix for JEP-200.

          [JENKINS-48932] Build-failure-analyzer afected by JEP-200 in Jenkins 2.102

          Remi Van Goethem created issue -
          Remi Van Goethem made changes -
          Epic Link New: JENKINS-47736 [ 186227 ]
          Remi Van Goethem made changes -
          Issue Type Original: Improvement [ 4 ] New: Bug [ 1 ]
          Summary Original: Build-failure-analyzer afected by JEP-200 New: Build-failure-analyzer afected by JEP-200 in Jenkins 2.102
          Oleg Nenashev made changes -
          Assignee Original: Tomas Westling [ t_westling ] New: Oleg Nenashev [ oleg_nenashev ]

          Oleg Nenashev added a comment -

          Thanks for the report! I will investigate it in 2hrs

          Oleg Nenashev added a comment - Thanks for the report! I will investigate it in 2hrs

          Jesse Glick added a comment -

          Looks like a simple whitelist addition for core offhand.

          Jesse Glick added a comment - Looks like a simple whitelist addition for core offhand.

          Oleg Nenashev added a comment -

          yup

          Oleg Nenashev added a comment - yup
          Oleg Nenashev made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Oleg Nenashev made changes -
          Component/s New: core [ 15593 ]

          Oleg Nenashev added a comment -

          I confirm that it should be fixed in the core. I will prepare the full list of collections. Making the plugin PCT compatible is complicated (https://github.com/jenkinsci/build-failure-analyzer-plugin/pull/81), maybe will fall back to the manual testing mode though it's hard to test all paths in the plugin.

          My plan is to offer a workaround resource file in the plugin so that the users do not get blocked by waiting for the core release

          Oleg Nenashev added a comment - I confirm that it should be fixed in the core. I will prepare the full list of collections. Making the plugin PCT compatible is complicated ( https://github.com/jenkinsci/build-failure-analyzer-plugin/pull/81 ), maybe will fall back to the manual testing mode though it's hard to test all paths in the plugin. My plan is to offer a workaround resource file in the plugin so that the users do not get blocked by waiting for the core release

            oleg_nenashev Oleg Nenashev
            rvangoethem Remi Van Goethem
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: