[JIRA] (JENKINS-13108) Removing P4CONFIG file on cleaning workspace

Alexey Larsky created JENKINS-13108:
---------------------------------------

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


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

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-13108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Larsky closed JENKINS-13108.
-----------------------------------

    Resolution: Fixed
   

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

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-13108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Larsky reopened JENKINS-13108:
-------------------------------------

   

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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160350#comment-160350 ]

Rob Petti commented on JENKINS-13108:
-------------------------------------

I'll add it to the list of excluded paths, but it should be noted that the perforce plugin doesn't even use this file, so it's generally not needed anyways (though I can see how it would be convenient).
               

> 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

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-13108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Petti reassigned JENKINS-13108:
-----------------------------------

    Assignee: Rob Petti
   

> 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

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-13108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

SCM/JIRA link daemon resolved JENKINS-13108.
--------------------------------------------

    Resolution: Fixed
   

> 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160351#comment-160351 ]

SCM/JIRA link daemon commented on JENKINS-13108:
------------------------------------------------

Code changed in jenkins
User: Rob Petti
Path:
 src/main/java/hudson/plugins/perforce/PerforceSCM.java
http://jenkins-ci.org/commit/perforce-plugin/7c0c24c8a2f4c65a2ac8046533c2adf093a1cb27
Log:
  [FIXED JENKINS-13108] exclude p4config file from wipe on checkout

note: Jenkins' built-in wipe out workspace functionality is not affected, and will still wipe the entire workspace (outside the scope of the p4 plugin)





               

> 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160353#comment-160353 ]

dogfood commented on JENKINS-13108:
-----------------------------------

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_perforce #201|http://ci.jenkins-ci.org/job/plugins_perforce/201/]
     [FIXED JENKINS-13108] exclude p4config file from wipe on checkout (Revision 7c0c24c8a2f4c65a2ac8046533c2adf093a1cb27)

     Result = SUCCESS
Rob Petti :
Files :
* src/main/java/hudson/plugins/perforce/PerforceSCM.java

               

> 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160614#comment-160614 ]

Alexey Larsky commented on JENKINS-13108:
-----------------------------------------

Thanks a lot. It work.
How add this exclude to Jenkins' built-in wipe?
               

> 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160614#comment-160614 ]

Alexey Larsky edited comment on JENKINS-13108 at 3/22/12 5:32 AM:
------------------------------------------------------------------

Thanks a lot. It work.
How add this exclude to Jenkins' built-in wipe?
Episodically we need clean builds for release build.
               
      was (Author: alexey_larsky):
    Thanks a lot. It work.
How add this exclude to Jenkins' built-in wipe?
                 

> 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160615#comment-160615 ]

Alexey Larsky commented on JENKINS-13108:
-----------------------------------------

Thanks a lot. It work.
How add this exclude to Jenkins' built-in wipe?
Episodically we need clean builds for release build.
               

> 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160616#comment-160616 ]

Rob Petti commented on JENKINS-13108:
-------------------------------------

You can file a feature request to add a generic 'exclude' option to workspace cleans, but it may be easier and faster to use a conditional pre-build step to do the clean manually using scripts:
https://wiki.jenkins-ci.org/display/JENKINS/pre-scm-buildstep
I haven't tested this myself, but it should work with a bit of effort.

Alternatively, you can just let jenkins clean it normally, and add a build step to recreate the .p4config file at build time. All the required config options are available in the environment, so it should be fairly easy to do.
eg.
{code}
echo P4PORT=$P4PORT > .p4config
echo P4USER=$P4USER >> .p4config
echo P4CLIENT=$P4CLIENT >> .p4config
echo P4PASSWD=$P4PASSWD >> .p4config
{code}
               

> 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160618#comment-160618 ]

Alexey Larsky commented on JENKINS-13108:
-----------------------------------------

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

       

    [ 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160633#comment-160633 ]

Rob Petti commented on JENKINS-13108:
-------------------------------------

You will likely need to write your own script in order to simulate 'svn clean'. There are plenty of resources for this online, such as the following *nix snippet:
{code}
find . -type f | p4 -x- files 2>&1 | sed -n -e 's/ - no such file(s).//p' | xargs -d '\n' rm
{code}
               

> 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