[Anthill-pro] Deactivate WF

[Eric Minick]

Curtis,

May I ask what the failure you see is?

-- Eric

Yanko, Curtis wrote:
> More thoughts on WF's, triggers and quiet periods
>  
> We are seeing a situation where We have a project with a our standard 
> 3 minute quite period and approximately 8 minute build time. I think 
> as a byproduct of your file locking approach (or maybe it is just SVN 
> in this case) we have a situation were a trigger that comes in after 
> the quiet period but during a build, fails.
>  
> So lets say BL #1 is running, #2 triggers and fails then #1 finishes 
> having succeeded. This is confusing to the consumer since BL2 fails 
> prior to BL1 success and we have are left with a change in the system 
> that didn't get built from the failed BL2.
>  
> Perhaps an internal lockable recourse to queue up build request. Once 
> released the WF could swallow up and subsequent triggers ad enter into 
> a quiet period where it would continue to swallow triggers and reset 
> the quiet period until it executes.
>  
> ===
> -Curt
> W: 860.702.9059
> M: 860.881.2050
>  
>
> ------------------------------------------------------------------------
> *From:* anthill-pro-bounces at lists.urbancode.com 
> [mailto:anthill-pro-bounces at lists.urbancode.com] *On Behalf Of *Yanko, 
> Curtis
> *Sent:* Tuesday, February 05, 2008 10:08 AM
> *To:* AnthillPro user and support list.
> *Subject:* [Anthill-pro] Deactivate WF
>
> Seems to me we need a way to de-activate a WF. We model WF's to 
> Branches within a project. Spinning up a new one is easy if we just 
> copy and make edits. But then when the branch goes idle we can only 
> delete it?? I'd like to be able to de-activate it so we can resurrect 
> it if needed but also so we are only presenting active branches to 
> team members. The ability to hide/show deactivated WF's would then 
> also be helpful so our team members with elevated permissions can 
> resurrect a WF if needed.
>  
> When copying WF's we really need the security permissions preserved 
> too. Otherwise the same people I have enabled to do the copy and edits 
> cannot then actually run it! Thus killing my self-service model for 
> Branch support.
>  
>  
> *Curtis Yanko*
> UnitedHealth Group IT
> Computer Services - AIS
> Source->Build->Deploy
> curt_yanko at uhc.com <mailto:curt_yanko at uhc.com>
> 	450 Columbus Blvd
> CT028-06SA
> Hartford, CT 06103
> work: 860.702.9059
> mobile: 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.
>
>
> 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.
> ------------------------------------------------------------------------
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>