[Anthill-pro] Copying artifacts to an external repository

[Jeff Rodgers (jerodger)]

Right now both systems are Windows, so we are doing a straight copy. I
first obtain the artifacts from Codestation and put them in a temporary
folder (temp/dsl_deploy). Then I thought I would use Groovy/Ant
integration to copy the file, but I wanted to write the Groovy script
in-place.

My Groovy script for that would be (after variable substitution): 
( new AntBuilder ( ) ).copy ( todir : /\\192.168.10.10\dsl\0.9.9/ ) {
fileset(dir : /temp/dsl_deploy/) }

Then I thought to use beanshell, but I don't know how to do a simple
copy with it.

Also, the target system may switch to use a web server front end. Then I
would use HTTP or FTP to transfer the file.


Jeff Rodgers
Cisco Remote Operations Services

-----Original Message-----
From: anthill-pro-bounces at caladin.urbancode.com
[mailto:anthill-pro-bounces at caladin.urbancode.com] On Behalf Of Eric
Minick
Sent: Wednesday, February 21, 2007 11:31 AM
To: anthill-pro at caladin.urbancode.com
Subject: Re: [Anthill-pro] Copying artifacts to an external repository

Jeff,

Good question. It would be helpful to know just a little bit more about
the external repository and how things are loaded into it.

Another option on the table is to load shell\ant\groovy script in as a
codestation project so that the loading tool can be used by several
different projects without checking it in to source control repeatedly.

Without knowing what the process of putting something in to this
repository is, it's hard to saw for sure what the best tool for the job
is.

Thanks,
Eric

Jeff Rodgers (jerodger) wrote:

> I would like to know the simplest way of automatically copying a set 
> of artifacts to an external repository in a non-originating workflow.
> I have done some research and there are a dizzying number of 
> possibilities. I could use an Ant script, a Groovy script, a Shell 
> script, a Beanshell snippet...
>  
> What I noticed is that the script should be somewhat self-contained in

> AHP3. That is, all of the information as to what to copy and where to 
> copy are in the Anthill project. Thus, if I can avoid checking a file 
> into source and just do this from Anthill, that would be preferable.
>  
> Then again, if this is a common task, how about making it a step type?
>  
>
> *Jeff Rodgers*
> *Software Engineer*
> **Customer Advocacy*
> *
> jerodger at cisco.com <mailto:jerodger at cisco.com> Phone :*(512) 340-3204*

> Mobile :*(512) 470-8267*
>
> 	
>
> **
> 9500 Amberglen Blvd.
> Austin, TX 78729
> United States
> www.cisco.com <http://www.cisco.com/>
>
> 	 
>
> This e-mail may contain confidential and privileged material for the 
> sole use of the intended recipient. Any review, use, distribution or 
> disclosure by others is strictly prohibited. If you are not the 
> intended recipient (or authorized to receive for the recipient), 
> please contact the sender by reply e-mail and delete all copies of 
> this message.
>
>
>  
>
>-----------------------------------------------------------------------
>-
>
>_______________________________________________
>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