[Anthill-pro] Deleting Perforce Clients in Source Configurations

[Steve Boone]

Chris,

You are correct that the Build Job does make some assumptions.  It basically
is a generic job, however it knows that the user will need a populate
workspace step and it adds a changelog step too.  If it is more cumbersome
for your project, then use the generic job.  There are many customers who do
prefer the generic job because it allows for full customization.

Regards,
Steve Boone

On 10/11/07, Chris Stoy <chris.stoy at redstorm.com> wrote:
>
>  Ok, to answer my own question (mostly because of my ignorance of what you
> can do in Anthill…)
>
>
>
> All I needed to do was to generate a Generic Job from the Build Job, and
> then just remove the Delete Clientspec step.  Now, if the Clientspec doesn't
> exist it is created, and if it does, nothing happens.
>
>
>
> Out of curiosity, are people using the Build jobs, or are they creating
> their own custom Generic jobs to do building?  It seems like the supplied
> Build Job makes some assumptions on how things are done and that you will
> almost always need to create a Generic job from it.  Not complaining…just
> trying to understand how this all works.
>
>
>
> Thanks,
>
>
>
>
>
> Chris.
>
>
>   ------------------------------
>
> *From:* anthill-pro-bounces at lists.urbancode.com [mailto:
> anthill-pro-bounces at lists.urbancode.com] *On Behalf Of *Chris Stoy
> *Sent:* Wednesday, October 10, 2007 10:55 AM
> *To:* AnthillPro user and support list.
> *Subject:* RE: [Anthill-pro] Deleting Perforce Clients in Source
> Configurations
>
>
>
> I would think having control over the creation/deletion of workspaces a
> "must have".   I'm not sure why you want to delete the clientspec all the
> time anyway.
>
>
>
> Ideally, it would be great if Anthill could generate a client workspace if
> one does not exist for an agent, but if it does, use the existing one.  This
> would make it possible to add/remove agents from the system without having
> to manually configure the Perforce clients for each machine.
>
>
>
> It is also confusing that there is a "Delete Clientspec" step in the Job
> trace even when the client isn't being deleted (as happens when using an
> existing Clientspec.)
>
>
>
> Thanks,
>
>
>
> Chris.
>
>
>
>
>  ------------------------------
>
> *From:* anthill-pro-bounces at lists.urbancode.com [mailto:
> anthill-pro-bounces at lists.urbancode.com] *On Behalf Of *Steve Boone
> *Sent:* Wednesday, October 10, 2007 10:29 AM
> *To:* AnthillPro user and support list.
> *Subject:* Re: [Anthill-pro] Deleting Perforce Clients in Source
> Configurations
>
>
>
> 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
>
>
>
> _______________________________________________
> 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/20071011/8c2fbc7e/attachment.htm