[Anthill-pro] Pushing and pulling buildlife artifactsfromthecodestation

[Steve Boone]

If you need access to dependency artifacts, you could take a look at the
Eclipse Plugins we offer.  That will allow you to resolve artifacts from
codestation to your local machine.

-Steve
On Thu, May 8, 2008 at 12:51 PM, Bell, Douglas <DBell at boingo.com> wrote:

>  Is this not possible? Is there a better way to get the project artifacts
> down to a local build so we don't have to rebuild the artifacts locally?
>
>
>  ------------------------------
>
> *From:* anthill-pro-bounces at lists.urbancode.com [mailto:
> anthill-pro-bounces at lists.urbancode.com] *On Behalf Of *Bell, Douglas
> *Sent:* Monday, May 05, 2008 9:08 AM
> *To:* AnthillPro user and support list.
> *Subject:* RE: [Anthill-pro] Pushing and pulling buildlife
> artifactsfromthecodestation
>
>
>
> We want to pull the artifacts from other project builds to our local
> development machines without having the check in what we are currently
> working on in our development environment.
>
>
>
> We do not want to build all dependent projects for each build (when they
> are already built and managed by AntHill).
>
>
>
> Project A
>
> |
>
> à Project B
>
>      |
>
>      à Project C
>
>
>
> In this instance we want to pull the artifacts from Project A and B when we
> change and build project C on our local development workstation.
>
>
>
> - Doug
>
>
>  ------------------------------
>
> *From:* anthill-pro-bounces at lists.urbancode.com [mailto:
> anthill-pro-bounces at lists.urbancode.com] *On Behalf Of *Steve Boone
> *Sent:* Friday, May 02, 2008 2:21 PM
> *To:* AnthillPro user and support list.
> *Subject:* Re: [Anthill-pro] Pushing and pulling buildlife artifacts
> fromthecodestation
>
>
>
> Doug,
>
> I think maybe I am missing what you are trying to do.
>
> You should not need an ant script at all.
>
> Your build runs, and produces artifacts.  We collect those artifacts in an
> artifact set (configured on the workflow) and use the Artifact deliver step
> to push them to CodeStation.
>
> Your secondary workflow runs, sets a working directory (the location on the
> agent we want to pull down the files) and then we use the "resolve my
> artifacts step" selecting the artifacts we want to retrieve from
> CodeStation.
>
> That's all you need to do.  Those files have now been pulled from
> CodeStation and are essentially "deployed"
>
> What is your goal with the Ant Task?
>
> On Fri, May 2, 2008 at 4:49 PM, Bell, Douglas <DBell at boingo.com> wrote:
>
> I'm getting closer…
>
>
>
> I have a non-originating workflow called artifact-retrieval-workflow that
> used a job configuration called artifact-retrieval-configuration that has
> one step "Resolve My Artifacts Step" in a project names
> enterprise-util-project. The ant tasks is as follows
>
>
>
> <target name="resolve" unless="resolve">
>
>             <taskdef name="resolve" classname=
> "com.urbancode.codestation2.client.ant.RetrieveDependenciesTask"/>
>
>             <resolve project="enterprise-util-project" workflow=
> "artifact-retrieval-workflow" server="xxxx" basedir="lib/" username="xxxx"
> password="xxxx" />
>
>       </target>
>
>
>
> I am getting a 404 on the resolve, however if I change the workflow
> parameter to my originating workflow I am able to get its dependencies.
>
>
>
> Any thoughts?
>
>
>
> Thanks,
>
>
>
> - Doug
>
>
>
>
>  ------------------------------
>
> *From:* Bell, Douglas
> *Sent:* Friday, May 02, 2008 1:30 PM
> *To:* 'AnthillPro user and support list.'
> *Subject:* RE: [Anthill-pro] Pushing and pulling buildlife artifacts from
> thecodestation
>
>
>
> Hi Steve,
>
>
>
> I've created a secondary non-originating workflow but don't see the Resolve
> my Artifacts step.
>
>
>
> - Doug
>
>
>  ------------------------------
>
> *From:* anthill-pro-bounces at lists.urbancode.com [mailto:
> anthill-pro-bounces at lists.urbancode.com] *On Behalf Of *Steve Boone
> *Sent:* Thursday, May 01, 2008 6:52 AM
> *To:* AnthillPro user and support list.
> *Subject:* Re: [Anthill-pro] Pushing and pulling buildlife artifacts from
> thecodestation
>
>
>
> Doug,
>
> I believe the cleaner solution would be to
>
> 1)  After the artifacts have been build.  Use the Deliver Artifacts Step,
> to send the files to Codestation.
>
> 2) on your secondary process (non-originating workflow) use the "Resolve my
> Artifacts" step to pull the files down from codestation.
>
> Let me know if I have been unclear, or confused you.
>
> Cheers,
> Steve Boone
>
> On Wed, Apr 30, 2008 at 5:12 PM, Bell, Douglas <DBell at boingo.com> wrote:
>
>
> Is it possible to deliver artifacts from a buildlife (a .jar in this
> case) to the Codestation and then pull it from the retrieve dependencies
> task in ant?
>
> I'm not seeing anything that tells me if I can or cannot do this. :/
>
> Thanks!
>
> - Doug
> _______________________________________________
> 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/20080515/81fb68ff/attachment.htm