After upgrading Jenkins to version 2.516.3, there was an unexpected admin monitor about there being unreadable data in pretty much every build in the system.

No such thing was mentioned in the 2.516.3 release notes or upgrade guide, so I am considering this a bug.

The error on the OldData overview page is CannotResolveClassException: libraryPath.

Looking in the build.xml files, this is found in

    <org.jenkinsci.plugins.workflow.libs.LibrariesAction plugin="pipeline-groovy-lib@752.vdddedf804e72">
      <libraries>
        <org.jenkinsci.plugins.workflow.libs.LibraryRecord>
          <name>my-library</name>
          <version>tags/1.2.3</version>
          <variables class="sorted-set">
            ...
          </variables>
          <trusted>true</trusted>
          <changelog>false</changelog>
          <libraryPath></libraryPath>
          <logString>my-library@tags/1.2.3</logString>
          <directoryName>...</directoryName>
        </org.jenkinsci.plugins.workflow.libs.LibraryRecord>
      </libraries>
    </org.jenkinsci.plugins.workflow.libs.LibrariesAction>

Given that the classes in question belong to this plugin, I'm reporting it here.

Perhaps this is because libraryPath is a constructor argument but there is no corresponding property, so the serialization doesn't know how to persist a value that the deserialization can use? No idea why that would have started to be an issue now though.

I mainly need to know whether it's safe to let Jenkins remove the setting or not; I expect it will be, given that the value is empty in all my builds, but I do not want to risk breaking our production environment.