@Mark when I click the "manage" button next to the error for a project 
named "Free_hand", I get the below message:

Manage Old Data
When there are changes in how data is stored on disk, Jenkins uses the 
following strategy: data is migrated to the new structure when it is 
loaded, but items/records are not resaved in the new format. This allows 
for downgrading Jenkins if necessary. However, it can also leave data on 
disk in the old format indefinitely. The table below lists items/records 
containing such data, and the Jenkins version(s) where the data structure 
was changed.

Sometimes errors occur while reading data (if a plugin adds some data and 
that plugin is later disabled, if migration code is not written for 
structure changes, or if Jenkins is downgraded after it has already written 
data not readable by the older version). These errors are logged, but the 
unreadable data is then skipped over, allowing Jenkins to start up and 
function properly.

Type    Name    Version
No old data was found.
Unreadable Data
It is ok to leave unreadable data in these items/records, as Jenkins will 
simply ignore it. To avoid the log messages at Jenkins startup you can 
permanently delete the unreadable data by resaving these items/records 
using the button below the list.

Type    Name    Error
hudson.model.FreeStyleProject   Free_hand       
CannotResolveClassException: com.sonyericsson.rebuild.RebuildSettings
hudson.model.FreeStyleBuild     Free_hand #1   
 CannotResolveClassException: com.sonyericsson.rebuild.RebuildAction
hudson.model.FreeStyleBuild     Free_hand #2   
 CannotResolveClassException: com.sonyericsson.rebuild.RebuildCause, 
CannotResolveClassException: com.sonyericsson.rebuild.RebuildAction
hudson.model.FreeStyleBuild     Free_hand #5   
 CannotResolveClassException: com.sonyericsson.rebuild.RebuildAction
hudson.model.FreeStyleBuild     Free_hand #3   
 CannotResolveClassException: com.sonyericsson.rebuild.RebuildCause, 
CannotResolveClassException: com.sonyericsson.rebuild.RebuildAction
hudson.model.FreeStyleBuild     Free_hand #7   
 CannotResolveClassException: com.sonyericsson.rebuild.RebuildAction
hudson.model.FreeStyleBuild     Free_hand #6   
 CannotResolveClassException: com.sonyericsson.rebuild.RebuildAction
hudson.model.FreeStyleBuild     Free_hand #4   
 CannotResolveClassException: com.sonyericsson.rebuild.RebuildCause, 
CannotResolveClassException: com.sonyericsson.rebuild.RebuildAction

On Saturday, May 2, 2020 at 9:27:53 PM UTC+5:30, Mark Waite wrote:
>
> Did you read the details behind the message that you have data in an 
> unreadable format?  When that appears on my Jenkins instance, I can click 
> the user interface button and it shows the details of the data that can't 
> be read.
>
> Usually the message will tell you why Jenkins cannot read the data.  For 
> example, if your job definition refers to a plugin that existed in the 
> previous installation and does not exist in the new installation, the 
> Jenkins will (correctly) report that the data cannot be read in the new 
> instance, since the plugin that reads that data is not installed.
>
> If you want stability on the Jenkins instance, then you might consider 
> using the long term support release rather than the weekly release.
>
> If you want the very latest improvements, then the weekly release is a 
> good choice.
>
> On Sat, May 2, 2020 at 9:30 AM Shifa Shaikh <shif...@gmail.com 
> <javascript:>> wrote:
>
>> Unable to import jobs of Jenkins old version: 2.224 to Jenkins New 
>> version: 2.234
>>
>> After I copy the job from old to new Jenkins home the Jenkins console UI 
>> throws this error:
>>
>> **You have data stored in older format and/or unreadable data.**
>>
>> Here is the old config.xml of a very simple job:
>>
>> <?xml version='1.1' encoding='UTF-8'?>
>> <flow-definition plugin="workflow-job@2.33">
>>   <actions/>
>>   <description></description>
>>   <keepDependencies>false</keepDependencies>
>>   <properties>
>>     <com.sonyericsson.rebuild.RebuildSettings plugin="rebuild@1.31">
>>       <autoRebuild>false</autoRebuild>
>>       <rebuildDisabled>false</rebuildDisabled>
>>     </com.sonyericsson.rebuild.RebuildSettings>
>>   </properties>
>>   <definition class=
>> "org.jenkinsci.plugins.workflow.cps.CpsFlowDefinition" plugin=
>> "workflow-cps@2.70">
>>     <script>node {
>>     agent any
>>     stages {
>>         stage(&apos;build user&apos;) {
>>
>>
>>             steps {
>>                      wrap([$class: &apos;BuildUser&apos;]) {
>>                          //echo &quot;${BUILD_USER}&quot;
>>                          def user = env.BUILD_USER_ID
>>             }
>>         }
>>     }
>> }
>>
>>
>> }</script>
>>     <sandbox>true</sandbox>
>>   </definition>
>>   <triggers/>
>>   <disabled>false</disabled>
>> </flow-definition>
>>
>> Next is the same job created in the newer version of Jenkins:
>>
>> <?xml version='1.1' encoding='UTF-8'?>
>> <flow-definition plugin="workflow-job@2.39">
>>   <description></description>
>>   <keepDependencies>false</keepDependencies>
>>   <properties>
>>     <com.sonyericsson.jenkins.plugins.bfa.model.ScannerJobProperty plugin
>> ="build-failure-analyzer@1.25.1">
>>       <doNotScan>false</doNotScan>
>>     </com.sonyericsson.jenkins.plugins.bfa.model.ScannerJobProperty>
>>   </properties>
>>   <definition class=
>> "org.jenkinsci.plugins.workflow.cps.CpsFlowDefinition" plugin=
>> "workflow-cps@2.80">
>>     <script>node {
>>     agent any
>>     stages {
>>         stage(&apos;build user&apos;) {
>>
>>
>>             steps {
>>                      wrap([$class: &apos;BuildUser&apos;]) {
>>                          //echo &quot;${BUILD_USER}&quot;
>>                          def user = env.BUILD_USER_ID
>>             }
>>         }
>>     }
>> }
>>
>>
>> }</script>
>>     <sandbox>true</sandbox>
>>   </definition>
>>   <triggers/>
>>   <disabled>false</disabled>
>> </flow-definition>
>>
>> Can someone please suggest how I can flawlessly import the jobs of the 
>> old Jenkins to the new Jenkins?
>>
>> I have about 75 complex Jenkins jobs and creating each manually on the 
>> new version of Jenkins will be trivial and could be error-prone.
>>
>> Can you please suggest?
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkins...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/d43e2995-ca92-42d1-9859-d86739f445aa%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/d43e2995-ca92-42d1-9859-d86739f445aa%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b54ffdfb-ef9c-44dc-8b38-6a8fe04f5aff%40googlegroups.com.

Reply via email to