[Anthill-pro] Building and deploying a dependency

[Steve Boone]

Emerson,

So let me see if I follow.

When you build A, it should start a build of B.  After A completes, you want
to run a deploy workflow on A, and once B is complete you want to run a
deploy workflow based on B.

There are a few ways to do this.

You could use the Run another workflow step, so that when A runs that
step,it will call a secondary workflow of your choice.  You could set that
up on the build job of A and B.

Then when A triggers a build of B, both will run deployments because they
have the "Run another workflow step"

I suppose one downside to this strategy is that the deploy will alwasys
happen, even if you build B separate from building A.

The other option, is to only deploy B if it was triggered by A.  To do that
we would have to write a script, but I believe it's doable.

Let me know what option sounds best to you.



On Tue, Mar 25, 2008 at 10:25 AM, emerson cargnin <
echofloripa.yell at gmail.com> wrote:

> Hi
>
> I have been wondering how I'm going to do the following:
>
> 1- When running a build workflow of A i want to run the build workflow of
> a dependency B
> 2- I want to run a deploy workflow of A based on the build done on 1.
> 3- I want to run a deploy workflow of B based on the dependency triggered
> on 1.
>
> The problem is: how I'm gonna make my dependency to run its own deploy
> secondary workflow? Secondary workflows don't have dependencies, so how
> would I trigger the deploy workflow of the dependency?
>
> Thanks
> Emerson
>
> _______________________________________________
> 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/20080325/b1f07c84/attachment.htm