-
Bug
-
Resolution: Fixed
-
Major
-
None
-
V0.21 of artifactdeployer plugin
I have the following setup:
1) deploy *.elf, *.map, *.gz to folder X:\foo\bar\Build_${SVN_REVISION_1}_${BUILD_NUMBER}\foo\bar
2) deploy some other *.elf, *.map, *.gz to folder X:\foo\bar\Build_${SVN_REVISION_1}_${BUILD_NUMBER}\baz\bar
3) deploy some other *.elf, *.map, *.gz to folder X:\foo\bar\Build_${SVN_REVISION_1}_${BUILD_NUMBER}\baz\quux
4) deploy .txt file to folder X:\foo\bar\Build_${SVN_REVISION_1}_${BUILD_NUMBER}
all of them have "delete artifacts" marked.
When the builds get deleted by jenkins (I only keep 15), the folder structure still exists, filling my artifacts deployment folder with junk.
My colleague uses a plain folder structure (X:\bar\baz\Build_${BUILD_NUMBER}${custom_var}) and his artifacts get deleted as well as the directories.
His project is running on the same jenkins instance as mine, so the problem seems to be the recursive deletion.
This was the reason, why I wanted the groovy script to work, so I could use that to finally delete the folders...
[JENKINS-15059] recursive deletion of deployment pathes not working correctly
Code changed in jenkins
User: Gregory Boissinot
Path:
src/main/java/org/jenkinsci/plugins/artifactdeployer/ArtifactDeployerPublisher.java
http://jenkins-ci.org/commit/artifactdeployer-plugin/1710ef63c7bfb8fe3a320b16fa53c1e39fcf13e8
Log:
Fix JENKINS-15059
Groovy script issue should be fixed from version 0.22.
This issue should be fixed from 0.23