[
https://issues.jenkins-ci.org/browse/JENKINS-13108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160618#comment-160618
]
Alexey Larsky edited comment on JENKINS-13108 at 3/22/12 8:35 AM:
------------------------------------------------------------------
We use self made tool for manage Perforce projects. It store in .p4config extra
information - project's bind with project's internal name:
FOO=InternalProjectName
This info not repeated in environment.
Also our team like to clean workspace by Jenkins build-in wipe. I need to
remove Jenkins build-in wipe or make it work.
I think what best way - add feature request.
It is possible simulate clean command in Perforce like "svn clean" ?
It can be better then wipe...
was (Author: alexey_larsky):
We use self made tool for manage Perforce projects. It store in .p4config
extra information - project's bind with project's internal name:
FOO=InternalProjectName
This info not repeated in environment.
Also our team like to clean workspace by Jenkins build-in wipe. I need to
remove Jenkins build-in wipe or make it work.
I think what best way - add feature request.
> Removing P4CONFIG file on cleaning workspace
> --------------------------------------------
>
> Key: JENKINS-13108
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13108
> Project: Jenkins
> Issue Type: Bug
> Components: perforce
> Affects Versions: current
> Reporter: Alexey Larsky
> Assignee: Rob Petti
>
> Cleaning workspace causing to remove local workspace config file.
> http://www.perforce.com/perforce/doc.current/manuals/cmdref/env.P4CONFIG.html
> http://www.jetbrains.com/idea/webhelp/using-multiple-perforce-depots-with-p4config.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
