[JIRA] (JENKINS-35447) bug on moveing pipeline projects into folder

[ilya.ros...@gmail.com (JIRA)]

Title: Message Title

ilya rosman edited a comment on JENKINS-35447   Re: bug on moveing pipeline projects into folder I can add some details. I found the same issue and googled this bug looking for java.io.FileNotFoundException: lastUnstableBuild (No such file or directory) First of all this issue is reproducible for the latest 5.18 folder_plugin version The root of this issue is the following. Let's assume we have the following job structure: ubuntu@ubuntu-xenial:~$ ls -l /var/lib/jenkins/jobs/ Master_TSDN_Controller_master XXX /builds/ total 40 drwxr-xr-x 2 1002 1002 4096 Feb 14 09:55 327 drwxr-xr-x 4 1002 1002 4096 Feb 14 10:14 328 drwxr-xr-x 4 1002 1002 4096 Feb 15 10:57 329 drwxr-xr-x 4 1002 1002 4096 Feb 17 08:29 330 drwxr-xr-x 4 1002 1002 4096 Feb 17 09:18 331 drwxr-xr-x 4 1002 1002 4096 Feb 20 13:55 332 drwxr-xr-x 4 1002 1002 4096 Feb 22 15:29 333 drwxr-xr-x 4 1002 1002 4096 Feb 27 11:18 334 lrwxrwxrwx 1 1002 1002    3 Feb 14 09:55 lastFailedBuild -> 327 lrwxrwxrwx 1 1002 1002    3 Feb 27 11:18 lastStableBuild -> 334 lrwxrwxrwx 1 1002 1002    3 Feb 27 11:18 lastSuccessfulBuild -> 334 lrwxrwxrwx 1 1002 1002    2 Jun 27  2016 lastUnstableBuild -> -1 lrwxrwxrwx 1 1002 1002    3 Feb 14 09:55 lastUnsuccessfulBuild -> 327 -rw-r--r-- 1 1002 1002    0 Jun 27  2016 legacyIds Corresponding links point to existing folders excepting lastUnstableBuild which points to non existing dir for now. It is supposed to be changed when UnstableBuild appears. For example in 332 build version We wanna move Master_TSDN_Controller_master XXX job to some newly created Test_Folder I used 3 cases how to handle it: 1) Using Jenkins GUI 2) Using post request curl -L -X POST http://10.229.55.117:8080/job/ Master_TSDN_Controller_master XXX /move/move?destination=/Test_Folder --user xxx:yyy 3) Using groovy script like that <code> def FOLDER_NAME = 'Test_Folder' def JOB_REGEX = 'Master_TSDN_Controller_master' import jenkins.* import jenkins.model.* import hudson.* import hudson.model.* jenkins = Jenkins.instance def folder = jenkins.getItemByFullName(FOLDER_NAME) if (folder == null) {   println "ERROR: Folder '$FOLDER_NAME' not found"   return } jenkins.items.grep { it.name =~ "${JOB_REGEX}" }.each { job ->   println "Moving '$job.name' to '$folder.name'"   Items.move(job, folder) } </code> All these methods transform links (lastFailedBuild, lastStableBuild, lastSuccessfulBuild, lastUnsuccessfulBuild) to dirs instead of their copying. In case of lastUnstableBuild -> -1 (points to nothing) it can not be transformed to dir and it is failed. Screenshot is attached. As result moving is broken. Job is copied (original is not deleted). Copied version has dirs instead of links P.s. As we can see the only 1 safest way for us to migrate jobs to folders is using cp -arp copying on jenkins linux master from jobs folder to Name_of_Folder/jobs. Then jenkins reloading/restarting Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.