[Anthill-pro] Building and deploying a dependency

[Steve Boone]

Emerson,

Have you tried using the |"Run Dependecy Workflow" step?  This will allow
you to run another build on ever dependent project.  So if B is dependent on
A, and when you build A, B is also build, you could use the "Run Dependency
Workflow" step and run the deploy workflow on all of A's dependencies (which
would be B).  Then you can also run the "Run another workflow step" on A,
and run it's own deploy workflow.  You casn set properties on the Run
Dependecny Workflow step.

If this isnt what you are looking for, let me know, and I will see what we
can come up with.

On Tue, Mar 25, 2008 at 12:43 PM, emerson cargnin <
echofloripa.yell at gmail.com> wrote:

> Steve
>
> On 25/03/2008, Steve Boone <sbb at urbancode.com> wrote:
>
> > 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.
>
>
> Not really. I want to run the build of B and then A when I trigger A
> build. Further then I want to deploy project A and would like project B to
> be deployed as well, using the same primary build created when B was
> triggered as a dependency.
>
> I can do it automatically, using the Run another workflow step",  the
> problem is that when I need to specify the environment, which will be
> different from CI when it's a build from tag case. What I need is to be able
> to find the dependencies, find its build life and then run the deploy
> secondary workflow of B using the same parameters (environment) used for A.
> Hope i haven't made it more confusing : )
>
> regards
> emerson
>
>
>
> > 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
> > >
> > >
> >
> > _______________________________________________
> > Anthill-pro mailing list
> > Anthill-pro at lists.urbancode.com
> > http://lists.urbancode.com/mailman/listinfo/anthill-pro
> >
> >
>
> _______________________________________________
> 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/20080328/ec0cfc3f/attachment.htm