[Anthill-pro] Lockable resource per environment

[Uldis Karlovs-Karlovskis]

This is my problem too. A wile ago we had specific Pre-condition Job script,
which was checking and waiting for specific lock. It worked fine for about
95% (sometimes two workflows were running in the same time anyway). After
few problems with newer Anthill version we were forced by AnthillPro to
remove that script and have only one Lockable Resource for one Workflow.

Regards,
Uldis, C. T. Co
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 emerson
cargnin
Sent: trešdiena, 2008. gada 23. aprīlī 14:43
To: AnthillPro user and support list.
Subject: [Anthill-pro] Lockable resource per environment

Hi

What's the best way to implement the following:
On my deployment workflow, one of the steps is to restart the webapp
server (resin). I want avoid anthill agents from restarting all agents
at the same time, to avoid any down time. For example, to restart 2 or
3 at a time.

I know I can create a lockable resource and apply it to a workflow.
This would stop the same workflow from running concurrently (please
correct if I'm wrong). But my requirement (and I it's guess a common
requirement) is to have this lock for agents in the same environment.

If there was a "acquire lock" and "release lock" steps, I could create
a lockable resource and use it to avoid restarting the servers at the
same time. But even then having a lockable resource per environment
would be more correct, as I wouldn't want the CI build to acquire the
same lock of the live deployments.

I think my best bet now is to create one lock per environment I want
to achieve this behaviour, and have a script to acquire the lock and
another one to release the lock.

Is it possible?

thanks
emerson
_______________________________________________
Anthill-pro mailing list
Anthill-pro at lists.urbancode.com
http://lists.urbancode.com/mailman/listinfo/anthill-pro