[Anthill-pro] Re: Circular dependencies and non-originatingworkflows

[Steve Boone]

Another approach could be to do both builds in the same Originating
workflow.

So when the workflow started, it to the build, and publish those artifacts,
then the second job would build the installables, and then publish them in a
separate artifact set.

If you keep them in separate originating workflows, then yes, they will
create a new build life, however you have have as many jobs (and those jobs
can all be build jobs) in the same workflow.

You will still have the traceability of those jobs on the buildlife page.

Cheers,
Steve

On Thu, May 22, 2008 at 12:48 PM, Peter Steele <psteele at maxiscale.com>
wrote:

> We take a different approach. The CI builds are mainly to provide early
> feedback on build breaks. The CI builds create deployable artifacts
> which users can install on systems, but for QA, we do a clean build from
> scratch, and the artifacts produced by those builds are what we pass on
> to QA. I've seen some weird problems with CI builds and I wouldn't trust
> them to use as official builds...
>
> -----Original Message-----
> From: anthill-pro-bounces at lists.urbancode.com
> [mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Heather
> Wells
> Sent: Thursday, May 22, 2008 9:23 AM
> To: anthill-pro at lists.urbancode.com
> Subject: [Anthill-pro] Re: Circular dependencies and
> non-originatingworkflows
>
> Steve,
>
> My thought was to keep the installer builds in the same build life as
> the CI builds.  So we'd have CI builds all day long on a repository
> trigger, then nightly builds that take the latest successful CI build,
> wrap it in an installer, and deliver it to QA.  My understanding was
> that if they were originating workflows, they'd start a new build life.
>
> I'm open to suggestions about better ways to do this.
>
> Thanks,
>
> Heather
>
> On May 22, 2008, at 8:48 AM, anthill-pro-request at lists.urbancode.com
> wrote:
>
> >
> > From: "Steve Boone" <sbb at urbancode.com>
> > Date: May 22, 2008 7:18:17 AM PDT
> > To: "AnthillPro user and support list."
> <anthill-pro at lists.urbancode.com
> > >
> > Subject: Re: [Anthill-pro] Circular dependencies and non-originating
> > workflows
> > Reply-To: "AnthillPro user and support list."
> <anthill-pro at lists.urbancode.com
> > >
> >
> >
> > 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
> >
> >
> >
>
> _______________________________________________
> 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/20080522/9c7a2ce0/attachment.htm