[Anthill-pro] Circular dependencies and non-originating workflows

[Steve Boone]

Heather,

Is there any reason you are using the Non-originating workflows to build the
installers?

I think you avoid the circular dependency if they are all originating
workflows, no?

Regards,
Steve Boone

On Mon, May 19, 2008 at 7:33 PM, Heather Wells <heather at semanticresearch.com>
wrote:

> I'm new to AnthillPro (switching from AnthillOS).  I'm getting used to the
> idea of Build Lives but I've run into a snag.  I looked through the mailing
> list archives but didn't see anything that solved the problem.
>
> I've got two originating workflows for CI builds of two different
> applications. Application A requires Application B to compile and I have the
> dependency set up in the workflow.
>
> I also have two non-originating workflows that build installers for the two
> applications.  The installer for Application B depends on the installer for
> Application A.  I can't set up dependencies in the non-originating workflow,
> but if I try setting them up in the originating workflows for the
> non-originating workflows to inherit I run into a circular dependency.
>
> Is there a better way to set this up?
>
>
>
> _______________________________________________
> 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/20080522/d3afd2f8/attachment.htm