[Anthill-pro] Composite workflow failing to run job on fixed agent

[Steve Boone]

Chris,

Yes, you could do that. I think the easier approach would be to simply add
the agent to the environment.  That way, it will run.  Then, you can
configure your other jobs to use agents based on environment properties, as
you suggested.

Regards,
Steve

On 10/4/07, Christopher Power <chrispower36 at gmail.com> wrote:
>
> Could I add the build machine to all of the environments, and then
> refactor my deployment agent selection script to not select that machine
> based on a variable set on the agent?
>
> On 10/4/07, Christopher Power <chrispower36 at gmail.com> wrote:
> >
> > No "somemachine" is the build machine where we have SVN installed, etc.,
> > and the selected environment is composed of machines that can have apps
> > deployed to them.
> >
> > Just saw this in the docs, doh!
> >
> > "The Fixed Agent Filter return a specified Agent. Use of this Agent
> > Filter is discouraged because that Agent may not be available in the
> > selected Environment, thus causing the Job to fail."
> >
> > Is there are way around this?
> >
> > I was trying to avoid creating an entirely seperate workflow to do this
> > (which in this case would be 2 unless I can pass a workflow property from
> > the first workflow to the second).
> >
> > Thanks,
> > Chris
> >
> >
> >  On 10/4/07, Ryan Smith <rws at urbancode.com> wrote:
> > >
> > > Chris,
> > >
> > > Is 'somemachine' in the same environment as what the workflow is
> > > running in?
> > >
> > > Ryan
> > >
> > > Christopher Power wrote:
> > > > I am attempting to create a composite "Deployment" workflow
> > > consisting
> > > > of 2 sequential jobs.  The first job is the deployment job which
> > > runs on
> > > > a set of machines selected by the user when the workflow is
> > > run.  The
> > > > next job is a release job set to run after the deploy job.  The
> > > release
> > > > job gets the change log, publishes the changelog, and stamps the
> > > build,
> > > > and is set to run on a Fixed Agent, in this case, "somemachine"
> > > which is
> > > > our build machine which has svn installed (changelog).  When I run
> > > the
> > > > Deployment workflow, the deploy job is run for the selected machines
> > > and
> > > > they succeed, then the release job is run and fails with the
> > > following
> > > > error message.
> > > >
> > > > 2007-10-04 17:01:10,160 ERROR wf1303 - Not enough agents were online
> > > for
> > > > Release (Fixed: somemachine)
> > > >
> > > > Any suggestions on what I might be doing incorrectly?  Am I using
> > > the
> > > > functionality properly?
> > > >
> > > > Thanks,
> > > > Chris
> > > >
> > > >
> > > >
> > > >
> > > ------------------------------------------------------------------------
> > > >
> > > > _______________________________________________
> > > > Anthill-pro mailing list
> > > > Anthill-pro at lists.urbancode.com
> > > > http://lists.urbancode.com/mailman/listinfo/anthill-pro
> > >
> > > --
> > > ===========================================================
> > > Ryan Smith.                     2044 Euclid Ave., Suite 600
> > > Lead Developer                  Cleveland, Ohio 44115
> > > Urbancode, Inc.
> > >                                email:   rws at urbancode.com
> > > web:     www.urbancode.com      phone:  216-858-9000
> > > web:     www.anthillpro.com      fax:    216-858-9602
> > > ===========================================================
> > > _______________________________________________
> > > 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/20071004/d7120143/attachment.htm