[Anthill-pro] Deployment and Artifacts

[Colfer, Brian]

All,

 

I have set up my builds typically in this method:

1 compile jar, war or exe

2 package the parts into a tar file with a unique name

3 copy the package to a holding directory (we call this a build depot)

4 push the tar to a test server on a *different* host 

5 notify ops that the system is ready for production and they get it
from the build depot

 

What I would like is some way to archive the package after ops has been
told to pick it up.  Would the artifact concept in anthill3 be a good
way to do this?  How might this work? Are there reasonable alternatives?

 

Thanks

 

Brian 

 

Brian Colfer

(m) 408-386-5601

AIM: bcolferSDC

YIM: briancolfer at yahoo.com

Skype: bcolferwork

 

Shopping.com (tm)
Find. Compare. Buy.
www.shopping.com <http://www.shopping.com/> 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20070607/fceeefb7/attachment.htm