[JIRA] Updated: (CCNET-212) Ignore missing client spec when updating/deleting a Perforce based project

The following issue has been updated:

    Updater: Mike Roberts 
(mailto:mike.b.roberts-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx)
       Date: Sun, 31 Oct 2004 11:32 PM
    Changes:
             Fix Version changed to 0.7.1
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.public.thoughtworks.org/browse/CCNET-212?page=history

---------------------------------------------------------------------
View the issue:
  http://jira.public.thoughtworks.org/browse/CCNET-212

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: CCNET-212
    Summary: Ignore missing client spec when updating/deleting a Perforce based 
project
       Type: Bug

     Status: Unassigned
   Priority: Major

 Original Estimate: 1 hour
 Time Spent: Unknown
  Remaining: 1 hour

    Project: CruiseControl .NET
 Components: 
             Source Control
   Fix Fors:
             0.7.1
   Versions:
             0.7

   Assignee: 
   Reporter: 

    Created: Fri, 29 Oct 2004 1:56 AM
    Updated: Sun, 31 Oct 2004 11:32 PM
Environment: Perforce, Windows

Description:
Sometimes when a project is being edited or deleted through the webapp it may 
fail for whatever reason.  The deletion/update of the project is not wrapped in 
any kind of transaction so the project is left in a unstable state - usually 
the client spec has been deleted but the project itself has not.  

Now when you try and delete/update the project again through the webapp, the 
logic assumes that it must delete the client spec before it continues.  If it 
can't delete the client spec (because it did so previously) it just fails with 
more errors.  

Manual intervention is required to create a dummy clientspec for CCNet to 
delete/update successfully when the project is edited through the webapp to 
restore the project information to a stable state.

Solution:  When attempting to delete the client spec, trap perforce errors if 
they arise and carry on with the logic of deleting/updating project state 
information.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click