On Sat, May 2, 2020 at 12:07 PM Mohtashim S <mohtash...@gmail.com> wrote:
> @Mark I guess you are pulling the same project in different versions of > Jenkins from github and they work fine in all the versions. I agree and > understand that they should and is actually working fine. > > No, that sample repository includes Freestyle jobs, Declarative Pipeline jobs with the job definition inside the config.xml file, Declarative Pipeline and Scripted Pipeline jobs with the job definition in SCM, and multibranch Pipeline jobs. > My problem is a little different. Do the below. > > Consider we have > > 1. Jenkins version "2.224" with Jenkins home directory as > /app/Jenkins/old_home > 2. Jenkins version "2.234" with Jenkins home directory as > /app/Jenkins/new_home > > Create a DSL job "Free_hand" in 2.224 with Execute Shell that prints > "hello" [ Note: no plugin dependencies ] > > Now, copy the "Free_hand" folder from inside the old version Jenkins job > -> "/app/Jenkins/old_home/jobs/Free_hand" and paste it in the > Jenkins_Home/jobs -> "/app/Jenkins/new_home/jobs/Free_hand" folder of > newer Jenkins_Home 2.234 > > You will not see the "Free_hand" project in the new version of Jenkins > even after the copy. > > I assume from this description that Jenkins was already running in the new location. Jenkins assumes it has control of the contents of the Jenkins home directory. Copying a new directory with a job definition into a running Jenkins instance will not be detected until the next Jenkins restart. > Restart the newer version of Jenkins. You will now see the Free_hand > project visible along with the error message in the notification that I'm > reporting. > > See my reply to Shifa Shaikh that describes the details of the messages seen in that case. If you have different details or more details, please provide them. Mark Waite > > On Sat, May 2, 2020 at 11:18 PM Mark Waite <mark.earl.wa...@gmail.com> > wrote: > >> Unfortunately, I can't duplicate the problem you're describing. Please >> provide precise steps that others can use to see the problem that you are >> seeing. >> >> Here are the steps that I tried: >> >> 1. Clear my Jenkins home directory >> 2. Create a branch >> >> <https://github.com/MarkEWaite/docker-lfs/tree/lts-with-plugins-for-shifa-shaikh>, >> create and run a docker image using Jenkins 2.222.3 with latest plugin >> versions - this creates a Jenkins home directory with over 150 jobs of >> various types >> 3. Stop that docker image >> 4. Create a new 2.224 branch >> >> <https://github.com/MarkEWaite/docker-lfs/tree/lts-with-plugins-for-shifa-shaikh-weekly>, >> create and run a docker image using Jenkins 2.224 with latest plugin >> versions - this reuses the same Jenkins home directory with over 150 jobs >> of various types >> 5. Confirm there were no warnings related to unreadable data or data >> format >> 6. Stop that docker image >> 7. Create a new 2.234 branch >> >> <https://github.com/MarkEWaite/docker-lfs/tree/lts-with-plugins-for-shifa-shaikh-weekly-latest>, >> create and run a docker image using Jenkins 2.234 with latest plugin >> versions - this reuses the same Jenkins home directory with over 150 jobs >> of various types >> 8. Confirm there were no warnings related to unreadable data or data >> format >> >> I'm not clear what you mean by "very basic Jenkins DSL job". The samples >> I've provided include: >> >> - Folders >> - Freestyle projects >> - Declarative Pipeline jobs defined inside the job itself >> - Scripted PIpeline jobs >> - Pipeline jobs defined in SCM >> - Multibranch Pipeline jobs >> >> Mark Waite >> >> On Sat, May 2, 2020 at 11:10 AM Shifa Shaikh <shifa...@gmail.com> wrote: >> >>> @Mark thank you for the reply but i beg to differ. >>> >>> Please understand that the issue is not what about a plugin reference >>> in the old versus in the newer version (whether you go for long term >>> release or weekly release) >>> >>> My Jenkins job has a single "execute shell" that prints "Hi" message. so >>> plugin dependency is not the reason for the error. >>> >>> You can replicate the issue on the said versions of Jenkins. Create a >>> very basic Jenkins DSL job in older version with no plugin dependencies. >>> Then copy the job to the newer stable Jenkins release. You will still see >>> the error I'm reporting. >>> >>> On Sat, May 2, 2020 at 9:27 PM Mark Waite <mark.earl.wa...@gmail.com> >>> 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 <shifa...@gmail.com> 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('build user') { >>>>> >>>>> >>>>> steps { >>>>> wrap([$class: 'BuildUser']) { >>>>> //echo "${BUILD_USER}" >>>>> 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('build user') { >>>>> >>>>> >>>>> steps { >>>>> wrap([$class: 'BuildUser']) { >>>>> //echo "${BUILD_USER}" >>>>> 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 jenkinsci-users+unsubscr...@googlegroups.com. >>>>> 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/CAO49JtGQc6Pn0Xm6cuer%3DH-1gp91H4U-M9eDjt_wCCvUQuRzTw%40mail.gmail.com >>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGQc6Pn0Xm6cuer%3DH-1gp91H4U-M9eDjt_wCCvUQuRzTw%40mail.gmail.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/CAJtox0nHt3v%3DcOuS2VWxYJ%2B2%2B_bCF9pYP0kRdoNjkyauzBh%3D6g%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/CAJtox0nHt3v%3DcOuS2VWxYJ%2B2%2B_bCF9pYP0kRdoNjkyauzBh%3D6g%40mail.gmail.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/CAO49JtGCCtzLsM55R4kZGEV4S1RWSqbe5TQ7z_4SPzd0RbAJ%2Bw%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGCCtzLsM55R4kZGEV4S1RWSqbe5TQ7z_4SPzd0RbAJ%2Bw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > R e g a r d s, > > <Mohtashim> > > <Subject Matter Expert> > mob: +91 9323657130 > > -- > 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/CAOy8S%3D-Hm88GFUH_HFUSiRBP30OaN%2B0CtbYyEQqKZsUjmOb96g%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CAOy8S%3D-Hm88GFUH_HFUSiRBP30OaN%2B0CtbYyEQqKZsUjmOb96g%40mail.gmail.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/CAO49JtFkOeg%2BQMWJ5rkcd-%3DA56UpsV3xwFweHHrbV3Z9J%3D_RMw%40mail.gmail.com.
