[Anthill-pro] Deleting Perforce Clients in Source Configurations

[Steve Boone]

Chris,

Currently these are the only two options available for our perforce
integration.  However, there is a workaround.  You could create your
clientspec manually, and then have anthill use the existing view.  This
would allow perforce just to sync the current changes.

Obviously the 20 minute sync is slowing you down, is this issue a show
stopper?  If this is a feature that is a 'must have' we can implement it for
you.  However, it's not something we can turn around instantly.  We will
have to develop the code, and test, etc.

Please let me know, and thanks for bringing this to our attention.
-Steve Boone

On 10/9/07, Chris Stoy < chris.stoy at redstorm.com> wrote:
>
>  Hello all,
>
>
>
> I'm evaluating Anthill Pro and am having some issues with project setup.
> I'm trying to set up a continuous build of a set of C++ and C# projects that
> is distributed across multiple agents.
>
>
>
> In the Source Configuration for a Project (I'm using a Perforce server) I
> have the option of either supplying an existing Clientpec or creating a new
> clientspec based on a template.  The problem is, if I tell it to create a
> new clientspec it will delete this spec when the Project is done building.
> The project I'm trying to build is huge and a full P4 sync takes over 20
> minutes, so deleting the clientspec every time I do a build is not
> acceptable.  It would be nice if I could create the clientspec automatically
> if it doesn't exist, but keep it around once the build is complete.  Is this
> possible?
>
>
>
> Thanks,
>
>
>
> Chris.
>
>
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20071010/10c52783/attachment.htm