[Anthill-pro] Resolving artifacts

[Christopher Power]

I verified I have an artifact deliver publisher setup, and that I am
delivering my artifacts in my originating build workflow.  After running the
build I can see the published artifacts on the "Artifacts" tab in the
buildlife's view.

When I run my deployment workflow, I set the working directory to be that of
the buildlife's ID, and then call the resolve my artifacts step.

I am still seeing the same message:
"Unable to create cache sync: The system cannot find the path specified -
could potentially result in threading issue"

Note:  The agent I am running the deploy workflow on is running on the same
machine as the server, if that makes a difference.

Chris


On 7/26/07, Steve Boone <sbb at urbancode.com> wrote:
>
> Christopher,
>
> Aside from resolving artifacts in your workflow, you also want to first
> make sure you are delivering artifacts from your build.  Do you have a
> Deliver Artifacts Step?  You would want this step to be a publisher in your
> build job.  Within your project, click on your build job, and then select
> the publisher tab.  If you do not already have a Deliver Artifact Set,
> please add one and select the Artifact Set you with to deliver.
>
> This is the step that actually publishes the artifacts to AnthillPro.
>
> So, to review, the Build creates the artifacts, and run the Deliver
> Artifact Set.  Your secondary workflow, runs the Resolve My Artifacts Step.
> The final piece is to configure your workflow for which artifacts to use.
> To do this, in your originating workflow, click the artifacts tab.  Here you
> can select which artifact set to use, and determine where to place these
> artifacts.  As a sanity check can you check out what you have set for your
> base directory.  It is relative to your working directory, so perhaps the
> path you have specified does not exist.
>
> Regards,
> Steve Boone
>
> On 7/25/07, Curtis Yanko <curt_yanko at uhc.com> wrote:
> >
> >
> > You are definitely publishing the artifacts during the originating
> > workflow? They show up on the Artifacts tab of the build life?
> >
> > Including that Ant script?... What we are learning is anything you want
> > or need in a secondary workflow has to have been published as an artifact
> > during the original build. I have a artifact type called Deploy Script where
> > we will keep the perl, .sh or whatever scripts will need during those deploy
> > workflows.
> >
> > Now if I could just resolve an artifact from a Windows BMS to a Unix
> > deploy agent!
> >
> > - Curtis Yanko
> > UnitedHealth Group IT
> > Mail Route: CT028-06SA
> > Internet email: curt_yanko at uhc.com
> > Office 860.702.9059
> > Cell 860.729.8171
> >
> >
> >
> >
> > This e-mail, including attachments, may include confidential and/or
> > proprietary information, and may be used only by the person or entity to
> >
> > which it is addressed. If the reader of this e-mail is not the intended
> > recipient or his or her authorized agent, the reader is hereby notified
> > that any dissemination, distribution or copying of this e-mail is
> > prohibited. If you have received this e-mail in error, please notify the
> >
> > sender by replying to this message and delete this e-mail immediately.
> >
> > _______________________________________________
> > 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/20070726/869bf8f6/attachment.htm