[JIRA] [core] (JENKINS-32455) Artifacts lost when renaming matrix project with custom Build record directory

2016-04-25 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32455 
 
 
 
  Artifacts lost when renaming matrix project with custom Build record directory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.


[JIRA] [core] (JENKINS-32455) Artifacts lost when renaming matrix project with custom Build record directory

2016-04-12 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-32455 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Artifacts lost when renaming matrix project with custom Build record directory  
 
 
 
 
 
 
 
 
 
 
Still cannot reproduce (Jenkins 2.0-rc-1 and Matrix Project Plugin 1.6). I configured the custom builds directory $JENKINS_HOME/builds/$ITEM_FULLNAME mostly for testing convenience. 
Created matrix project 'foo', with axis FOO and value 'bar', built twice, renamed to foo-renamed, built a third time, and this is on disk: 

 
foo-renamed
foo-renamed/1
foo-renamed/1/build.xml
foo-renamed/1/changelog.xml
foo-renamed/1/log
foo-renamed/2
foo-renamed/2/build.xml
foo-renamed/2/changelog.xml
foo-renamed/2/log
foo-renamed/3
foo-renamed/3/build.xml
foo-renamed/3/changelog.xml
foo-renamed/3/log
foo-renamed/FOO=bar
foo-renamed/FOO=bar/1
foo-renamed/FOO=bar/1/archive
foo-renamed/FOO=bar/1/archive/foo
foo-renamed/FOO=bar/1/build.xml
foo-renamed/FOO=bar/1/changelog.xml
foo-renamed/FOO=bar/1/log
foo-renamed/FOO=bar/2
foo-renamed/FOO=bar/2/archive
foo-renamed/FOO=bar/2/archive/foo
foo-renamed/FOO=bar/2/build.xml
foo-renamed/FOO=bar/2/changelog.xml
foo-renamed/FOO=bar/2/log
foo-renamed/FOO=bar/3
foo-renamed/FOO=bar/3/archive
foo-renamed/FOO=bar/3/archive/foo
foo-renamed/FOO=bar/3/build.xml
foo-renamed/FOO=bar/3/changelog.xml
foo-renamed/FOO=bar/3/log
foo-renamed/FOO=bar/lastStableBuild
foo-renamed/FOO=bar/lastSuccessfulBuild
foo-renamed/FOO=bar/legacyIds
foo-renamed/lastFailedBuild
foo-renamed/lastStableBuild
foo-renamed/lastSuccessfulBuild
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.


[JIRA] [core] (JENKINS-32455) Artifacts lost when renaming matrix project with custom Build record directory

2016-04-12 Thread russell.gal...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Gallop commented on  JENKINS-32455 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Artifacts lost when renaming matrix project with custom Build record directory  
 
 
 
 
 
 
 
 
 
 
> Try with an instance that doesn't have SCM Sync Configuration and try again. 
I've disabled SCM Sync (+metadata, multijob, envinject and job config history) and still see the same behaviour (now with 1.642.4). 
Build 1 was before rename, build 2 is after rename. Log: 

 

Apr 12, 2016 11:33:45 AM INFO hudson.model.Run execute
JENKINS-32455-testd_renamed/FOO=bar #1 main build action completed: SUCCESS
Apr 12, 2016 11:33:46 AM INFO hudson.model.Run execute
JENKINS-32455-testd_renamed #1 main build action completed: SUCCESS
Apr 12, 2016 11:33:56 AM INFO hudson.model.Run execute
JENKINS-32455-testd_renamed/FOO=bar #2 main build action completed: SUCCESS
Apr 12, 2016 11:33:57 AM INFO hudson.model.Run execute
JENKINS-32455-testd_renamed #2 main build action completed: SUCCESS
 

 
And these are the resulting files (using git bash on Windows): 

 

JENKINS-32455-testd/
JENKINS-32455-testd/FOO=bar/
JENKINS-32455-testd/FOO=bar/builds/
JENKINS-32455-testd/FOO=bar/builds/1/
JENKINS-32455-testd/FOO=bar/builds/1/archive/
JENKINS-32455-testd/FOO=bar/builds/1/archive/afile.txt
JENKINS-32455-testd/FOO=bar/builds/1/build.xml
JENKINS-32455-testd/FOO=bar/builds/1/changelog.xml
JENKINS-32455-testd/FOO=bar/builds/1/log
JENKINS-32455-testd/FOO=bar/builds/lastStableBuild
JENKINS-32455-testd/FOO=bar/builds/lastSuccessfulBuild
JENKINS-32455-testd/FOO=bar/builds/legacyIds
JENKINS-32455-testd_renamed/
JENKINS-32455-testd_renamed/builds/
JENKINS-32455-testd_renamed/builds/1/
JENKINS-32455-testd_renamed/builds/1/build.xml
JENKINS-32455-testd_renamed/builds/1/changelog.xml
JENKINS-32455-testd_renamed/builds/1/log
JENKINS-32455-testd_renamed/builds/2/
JENKINS-32455-testd_renamed/builds/2/build.xml
JENKINS-32455-testd_renamed/builds/2/changelog.xml
JENKINS-32455-testd_renamed/builds/2/log
JENKINS-32455-testd_renamed/builds/lastFailedBuild
JENKINS-32455-testd_renamed/builds/lastStableBuild
JENKINS-32455-testd_renamed/builds/lastSuccessfulBuild
JENKINS-32455-testd_renamed/builds/legacyIds
JENKINS-32455-testd_renamed/FOO=bar/
JENKINS-32455-testd_renamed/FOO=bar/builds/
JENKINS-32455-testd_renamed/FOO=bar/builds/2/
JENKINS-32455-testd_renamed/FOO=bar/builds/2/archive/
JENKINS-32455-testd_renamed/FOO=bar/builds/2/archive/afile.txt
JENKINS-32455-testd_renamed/FOO=bar/builds/2/build.xml
JENKINS-32455-testd_renamed/FOO=bar/builds/2/changelog.xml
JENKINS-32455-testd_renamed/FOO=bar/builds/2/log
JENKINS-32455-testd_renamed/FOO=bar/builds/lastStableBuild
JENKINS-32455-testd_renamed/FOO=bar/builds/lastSuccessfulBuild
 

 
Clarified the original description to say that this was a user-defined axis. 
 
 
 
 
 
 
 
 
 
 
 
 

 

[JIRA] [core] (JENKINS-32455) Artifacts lost when renaming matrix project with custom Build record directory

2016-04-12 Thread russell.gal...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Gallop updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32455 
 
 
 
  Artifacts lost when renaming matrix project with custom Build record directory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Gallop 
 
 
 
 
 
 
 
 
 
 Using a custom build record directory means that artifacts are lost when renaming a matrix project.I have set up:Build Record Root Directory d:/artifacts/$\{ITEM_FULL_NAME\}/builds/And a matrix job: "Rename_test" which has one  user-defined  axis "FOO" with one value "bar".which executes a Windows batch command: "echo %BUILD_TAG% > afile.txt"And Archives the artifact afile.txt.I run this a couple of times to create some artifacts then rename the job to "Rename_test_new_name". The artifacts (and other per-configuration build data) are not moved so the folder: d:/artifacts now has "Rename_test" and "Rename_test_new_name". New artifacts are created in the new name, old artifacts are still in the old folder.I think that this may be to do with how ITEM_FULL_NAME works. With the default "Build record root directory" ($\{ITEM_ROOTDIR\}/builds) the per configuration data is stored in:Rename_test/configurations/axis-FOO/bar/buildsWith the build record root directory changed to "d:/artifacts/$\{ITEM_FULL_NAME\}/builds/" they are stored in:Rename_test/FOO=bar/builds 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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://gr

[JIRA] [core] (JENKINS-32455) Artifacts lost when renaming matrix project with custom Build record directory

2016-03-19 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-32455 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Artifacts lost when renaming matrix project with custom Build record directory  
 
 
 
 
 
 
 
 
 
 
I cannot reproduce what is reported here. When I rename the job, the builds directory also gets renamed. 
Try with an instance that doesn't have SCM Sync Configuration and try again. 
Another option could be weird file locking on Windows, but that should result in exceptions being logged. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.


[JIRA] [core] (JENKINS-32455) Artifacts lost when renaming matrix project with custom Build record directory

2016-03-15 Thread russell.gal...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Gallop commented on  JENKINS-32455 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Artifacts lost when renaming matrix project with custom Build record directory  
 
 
 
 
 
 
 
 
 
 
No exception in the log (I've removed messages not related to this job). Build #3 was pre-rename though the log seems to use the new name. (now with jenkins 1.642.2). 

 

JENKINS_32455_test_renamed/FOO=bar #3 main build action completed: SUCCESS
Mar 15, 2016 9:42:58 AM INFO hudson.model.Run execute
JENKINS_32455_test_renamed #3 main build action completed: SUCCESS
...
Mar 15, 2016 9:49:38 AM INFO hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness queueChangeSet
Queue of changeset A jobs/JENKINS_32455_test/config.xml
 aborted (scm manipulator not settled !)
Mar 15, 2016 9:49:39 AM INFO hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness queueChangeSet
Queue of changeset A jobs/JENKINS_32455_test/config.xml
 aborted (scm manipulator not settled !)
Mar 15, 2016 9:49:40 AM INFO hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness queueChangeSet
Queue of changeset A jobs/JENKINS_32455_test/config.xml
 aborted (scm manipulator not settled !)
...
Mar 15, 2016 9:53:04 AM INFO hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness queueChangeSet
Queue of changeset D jobs/JENKINS_32455_test
 aborted (scm manipulator not settled !)
...
Mar 15, 2016 10:04:41 AM INFO hudson.model.Run execute
JENKINS_32455_test_renamed/FOO=bar #4 main build action completed: SUCCESS
Mar 15, 2016 10:04:42 AM INFO hudson.model.Run execute
JENKINS_32455_test_renamed #4 main build action completed: SUCCESS
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 option

[JIRA] [core] (JENKINS-32455) Artifacts lost when renaming matrix project with custom Build record directory

2016-03-14 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-32455 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Artifacts lost when renaming matrix project with custom Build record directory  
 
 
 
 
 
 
 
 
 
 
There should be an exception in the Jenkins log, as Job#renameTo handles the build directory case. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.


[JIRA] [core] (JENKINS-32455) Artifacts lost when renaming matrix project with custom Build record directory

2016-01-14 Thread russell.gal...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Gallop updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32455 
 
 
 
  Artifacts lost when renaming matrix project with custom Build record directory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Gallop 
 
 
 
 
 
 
 
 
 
 Using a custom build record directory means that artifacts are lost when renaming a matrix project.I have set up:Build Record Root Directory d:/artifacts/$\{ITEM_FULL_NAME\}/builds/And a matrix job: "Rename_test" which has one axis "FOO" with one value "bar".which executes a Windows batch command: "echo %BUILD_TAG% > afile.txt"And Archives the artifact afile.txt.I run this a couple of times to create some artifacts then rename the job to "Rename_test_new_name". The artifacts (and other per-configuration build data) are not moved so the folder: d:/artifacts now has "Rename_test" and "Rename_test_new_name". New artifacts are created in the new name, old artifacts are still in the old folder.I think that this may be to do with how ITEM_FULL_NAME works. With the default "Build record root directory" ($ \ {ITEM_ROOTDIR \ }/builds) the per configuration data is stored in:Rename_test/configurations/axis-FOO/bar/buildsWith the build record root directory changed to "d:/artifacts/$ \ {ITEM_FULL_NAME \ }/builds/" they are stored in:Rename_test/FOO=bar/builds 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.go

[JIRA] [core] (JENKINS-32455) Artifacts lost when renaming matrix project with custom Build record directory

2016-01-14 Thread russell.gal...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Gallop updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32455 
 
 
 
  Artifacts lost when renaming matrix project with custom Build record directory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Gallop 
 
 
 
 
 
 
 
 
 
 Using a custom build record directory means that artifacts are lost when renaming a matrix project.I have set up:Build Record Root Directory d:/artifacts/$ \ {ITEM_FULL_NAME \ }/builds/And a matrix job: "Rename_test" which has one axis "FOO" with one value "bar".which executes a Windows batch command: "echo %BUILD_TAG% > afile.txt"And Archives the artifact afile.txt.I run this a couple of times to create some artifacts then rename the job to "Rename_test_new_name". The artifacts (and other per-configuration build data) are not moved so the folder: d:/artifacts now has "Rename_test" and "Rename_test_new_name". New artifacts are created in the new name, old artifacts are still in the old folder.I think that this may be to do with how ITEM_FULL_NAME works. With the default "Build record root directory" (${ITEM_ROOTDIR}/builds) the per configuration data is stored in:Rename_test/configurations/axis-FOO/bar/buildsWith the build record root directory changed to "d:/artifacts/${ITEM_FULL_NAME}/builds/" they are stored in:Rename_test/FOO=bar/builds 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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

[JIRA] [core] (JENKINS-32455) Artifacts lost when renaming matrix project with custom Build record directory

2016-01-14 Thread russell.gal...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Gallop created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32455 
 
 
 
  Artifacts lost when renaming matrix project with custom Build record directory  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi 
 
 
 

Components:
 

 core, matrix-project-plugin 
 
 
 

Created:
 

 14/Jan/16 3:05 PM 
 
 
 

Environment:
 

 1.625.1 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Russell Gallop 
 
 
 
 
 
 
 
 
 
 
Using a custom build record directory means that artifacts are lost when renaming a matrix project. 
I have set up: Build Record Root Directory d:/artifacts/$ {ITEM_FULL_NAME}/builds/  And a matrix job: "Rename_test" which has one axis "FOO" with one value "bar". which executes a Windows batch command: "echo %BUILD_TAG% > afile.txt" And Archives the artifact afile.txt.  I run this a couple of times to create some artifacts then rename the job to "Rename_test_new_name". The artifacts (and other per-configuration build data) are not moved so the folder: d:/artifacts now has "Rename_test" and "Rename_test_new_name". New artifacts are created in the new name, old artifacts are still in the old folder.  I think that this may be to do with how ITEM_FULL_NAME works. With the default "Build record root directory" (${ITEM_ROOTDIR}/builds) the per configuration data is stored in: Rename_test/configurations/axis-FOO/bar/builds  With the build record root directory changed to "d:/artifacts/${ITEM_FULL_NAME}