[Anthill-pro] Agent Locks

[Yanko, Curtis]

While I like the concept it doesn't really work for us. I'd like to see
a simple WF lock (originating) that would also be invoked by a secondary
workflow.
 
Since we have Solaris, AIX and Windows and they all build in a NAS it is
possible to have a WF building in *nix and not prevent a windows agent
from firing up another build since the paths are different. A simpler WF
lock could avoid this. I realize some people may have an architecture
where running the same OWF on two different agents may have value so it
should be a be a check box sort of thing.
 
Additionally, I more and more want to split off some processes from the
main build to drive down our build times. Stuff like publishing file and
maven site reports are getting lengthy. I'd like the OWF to just build
and get the notification out but also trigger a secondary WF to do the
site reports and publish files (a sort of lazy algorithm ). Since I need
the secondary to run "in" the working dir of the originating work flow
It would need to lock the OWF also (which should also eat triggers! ).
 
===
-Curt
W: 860.702.9059
M: 860.881.2050
 



This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to 
which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the 
sender by replying to this message and delete this e-mail immediately.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20080701/1fa80605/attachment-0001.htm