• Type: Bug
• Resolution: Unresolved
• Priority: Major
• Component/s: p4-plugin
• Labels:

  • P4_SUPPORT

[JENKINS-67331] "DELETE generated files" does not work when the workspace has several view mappings

Paweł Cichocki created issue - 2021-12-08 18:27

Paweł Cichocki made changes - 2021-12-08 18:29

Description

Original: {{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.**

New: {{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.**

Paweł Cichocki made changes - 2021-12-08 18:47

Description

Original: {{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.**

New: {{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.**

Paweł Cichocki made changes - 2021-12-08 18:47

Description

Original: {{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.**

New: {{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.**

Karl Wirth made changes - 2021-12-10 13:25

Labels

New: P4_SUPPORT