[Anthill-pro] Deleting Perforce Clients in Source Configurations

Thu Oct 11 01:35:49 CDT 2007

Yes I`m talking about only one workflow. It have trigger which shoots out
every 5 minutes. The source code is not small, so workspace populating and
changelog getting and publish sometimes can take up to 5 minutes. I wanted
to delete changelist after build but then every build is failing. What
really happens in AntHill - the first build is shooted, anthill checks if
there are source changes and starts my build. After 5 minutes while first
build is running there are shooted next build (for the same workflow so the
lock is the same). AntHill again checks if there is changed source, if yes,
waits for first build and then runs second build. The issue is in this check
for source changes because anthill takes my configured perforce client
template, tries to create new one client, checks source and deletes perforce
client. So truly it deletes perforce client for first build. So if this had
happened when the first build tries to delete its perforce client it fails.

Now I have configured for my build that Delete ClientSpec step is ignored
for failures but this is not right.

In other project I have avoided this issue and created my own procedure to
check for source, so the lock is set on Perforce ClientSpec which means
there can`t be checked for source changes while other build is doing
something with source.

I hope I was clear enough.

I`m using version 3.3.2 but imo this is not fixed yet.

Uldis Karlovs-Karlovskis, C. T. Co

 <mailto:uldis.karlovs-karlovskis at ctco.lv> uldis.karlovs-karlovskis at ctco.lv

-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Steve Boone
Sent: trešdiena, 2007. gada 10. oktobrī 19:44
To: AnthillPro user and support list.
Subject: Re: [Anthill-pro] Deleting Perforce Clients in Source
Configurations

Uldis,

How are you using the locks?  If you create a lock, and then set it on the
workflow it should keep those jobs from running over each other.  You want
to make sure you have the same lock being used throughout the project.  If
you have different locks set, then it will not work. 

Regards,
Steve Boone

On 10/10/07, Uldis Karlovs-Karlovskis < uldisk at ctco.lv> wrote:

Steve,

Is it possible to somehow switch off ClientSpec recreation when build is
determining for new changes in source control? I have configured all
features (locking, more than one build agent, clientspec is generating from
template on every build) for my workflow but any way there is situations
when while running build is population workspace or getting changelist,
other trigger shoots out and checks for new changes so it deletes
clientspec. This is a bug imo.

Uldis Karlovs-Karlovskis, C. T. Co

 <mailto:uldis.karlovs-karlovskis at ctco.lv> uldis.karlovs-karlovskis at ctco.lv

-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Steve Boone
Sent: trešdiena, 2007. gada 10. oktobrī 17:29
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
<mailto: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/b7ed0c2b/attachment.htm