-
Bug
-
Resolution: Unresolved
-
Major
In case you use perforce View Mappings to obtain several disjoint parts of your project as in:
//repo/project/engine/... //jenkins${NODE_NAME}${JOB_NAME}${EXECUTOR_NUMBER}/engine/...
//repo/project/libx/... //jenkins${NODE_NAME}${JOB_NAME}${EXECUTOR_NUMBER}/libx/...
//repo/project/engine_test_files/... //jenkins${NODE_NAME}${JOB_NAME}${EXECUTOR_NUMBER}/engine_test_files/...
The option "DELETE generated files" does nothing (the files are not deleted).
It might be useful to note that in such a case the p4 clean command also does not work when ran in the workspace root for example /var/jenkins/workspace/EngineTest. However it will succeed if ran independently in /var/jenkins/workspace/EngineTest/engine, /var/jenkins/workspace/EngineTest/libx, and /var/jenkins/workspace/EngineTest/engine_test_files, nevertheless still leaving the root workspace folder not cleaned.**
Hi pcatvi - For me this seems to be working. For example I created a Freestyle project with 'Auto Clean and Sync'. My view is:
and in my build job I add files to the 'project1' subdirectory.
When the job executes the next time I see these files being removed:
If I don not tick "DELETE generated files" then the build assets do not get deleted.
Would you like me to email you directly so I can get more information about your Perforce server, location of these files and the way you have your job setup?