[JIRA] Resolved: (HUDSON-8118) Wipe Out Workspace for P4 broken for multiple nodes

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Resolved: (HUDSON-8118) Wipe Out Workspace for P4 broken for multiple nodes

Kohsuke Kawaguchi
Administrator

     [ http://issues.hudson-ci.org/browse/HUDSON-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

rpetti resolved HUDSON-8118.
----------------------------

    Resolution: Fixed

Fixed in head revision.

> Wipe Out Workspace for P4 broken for multiple nodes
> ---------------------------------------------------
>
>                 Key: HUDSON-8118
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-8118
>             Project: Hudson
>          Issue Type: Bug
>          Components: perforce
>    Affects Versions: current
>            Reporter: jpshackelford
>            Assignee: rpetti
>
> From HUDSON-5777 I gather that the Wipe Out Workspace function removes workspace files and then toggles a one-time Force Sync in order to sync the files back in the next build, since the P4 have table is now out of sync with the workspace contents. If this is the case, it explains an issue that we see frequently.
> 1. User triggers Wipe Out Workspace against node A. Files removed. One time force sync option toggled.
> 2. User initiates a new build of the job and it runs on Node B. Plugin uses force sync instead of normal sync. Build successful.
> 3. Some time later... SCM polling triggers build on node A. Plugin uses typical sync and retrieves only files changed since Wipe Out Workspace executed. Build fails.
> The solution is to change the implementation of "Wipe Out Workspace" such that:
> 1. We rm -rf the workspace (in a manner of speaking)
> 2. We run p4 flush //workspace_name/...#0 to update the have table
> 3. We do not schedule a force sync. The have table will now be up-to-date and a regular p4 sync will bring down all of the files as expected.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira