[Anthill-pro] Restricting non-originating workflows

[Eric Minick]

Jeff,

When the project deviates that far during the branch, you could do a 
project copy to start the new project and work from that.

Regards,

Eric

Jeff Rodgers (jerodger) wrote:
> I chose this approach because it was the simplest to implement (at
> first). I was only supporting a single set of developers and the
> branches were all built the same way. Now that the branches are
> diverging, I am having second thoughts. But for most of the builds, all
> I needed was to add new Source Configurations and Stamping Strategies,
> copy the workflows and add the Source Configuration and Stamps to the
> new workflow.
>  
> Now I have a project that is branched off of the same source, but has
> changed the build and deployment strategies. Also the group of
> developers is different. So for this it probably would have been better
> to create a new AHP3 project.
>  
> Jeff Rodgers
> Cisco Remote Operations Services
>  
>
>
> ________________________________
>
> 	From: anthill-pro-bounces at caladin.urbancode.com
> [mailto:anthill-pro-bounces at caladin.urbancode.com] On Behalf Of Curtis
> Yanko
> 	Sent: Thursday, July 26, 2007 12:15 PM
> 	To: AnthillPro user and support list.
> 	Subject: Re: [Anthill-pro] Restricting non-originating workflows
> 	
> 	
>
> 	Jeff, 
> 	
> 	It is interesting that you chose to support branching within a
> single project by way of workflows. I have been back and forth on this
> myself but am currently in the one branch per project (ahp's idea of a
> project anyway) camp. It was precisely for issues like your secondary
> workflow conundrum that I decided workflows weren't a suitable way to
> support branching. It seemed to me that you'd have to have statuses for
> each branch as well though I suspect some creativity could be applied
> there. 
> 	
> 	Do you perceive any advantages beyond some savings in
> administration? 
> 	
> 	- Curtis Yanko
> 	UnitedHealth Group IT
> 	Mail Route: CT028-06SA
> 	Internet email: curt_yanko at uhc.com
> 	Office 860.702.9059
> 	Cell 860.729.8171
> 	
> 	
> 	
> 	
> "Jeff Rodgers \(jerodger\)" <jerodger at cisco.com> 
> Sent by: anthill-pro-bounces at caladin.urbancode.com 
>
> 07/25/2007 10:55 AM 
> Please respond to
> "AnthillPro user and support list." <anthill-pro at caladin.urbancode.com>
>
>
> To
> <anthill-pro at caladin.urbancode.com> 
> cc
> Subject
> [Anthill-pro] Restricting non-originating workflows
>
> 	
>
>
>
> 	Is there a way to restrict non-originating workflows to only be
> allowed
> 	on specific originating workflows? I have a project with several
> 	branches that have originating workflows for each branch. There
> are some
> 	specialized non-originating workflows that I would like to
> create to run
> 	on the different branches but not others.
> 	
> 	
> 	
> 	Jeff Rodgers
> 	Software Engineer
> 	Customer Advocacy
> 	
> 	jerodger at cisco.com
> 	Phone :(512) 340-3204
> 	Mobile :(512) 470-8267
> 	
> 	
> 	
> 	9500 Amberglen Blvd.
> 	Austin, TX 78729
> 	United States
> 	www.cisco.com <http://www.cisco.com/>
> 	
> 	
> 	This e-mail may contain confidential and privileged material for
> the
> 	sole use of the intended recipient. Any review, use,
> distribution or
> 	disclosure by others is strictly prohibited. If you are not the
> intended
> 	recipient (or authorized to receive for the recipient), please
> contact
> 	the sender by reply e-mail and delete all copies of this
> message.
> 	
> 	
> 	  
> 	_______________________________________________
> 	Anthill-pro mailing list
> 	Anthill-pro at lists.urbancode.com
> 	http://lists.urbancode.com/mailman/listinfo/anthill-pro 
> 	
> 	
> 	
> 	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
>