[Anthill-pro] Deployment and Artifacts

[Eric Minick]

Brian,

In the artifact selection area, we don't yet support scripts. This is 
because the codestation rules can be used outside Anthill for local 
development builds and the scripts can't be resolved there. Anyway, you 
would set the directory those files are found in and pick up MT_*.tgz 
and CMI_*.tgz.

The artifact resolution should be done in a secondary workflow for a 
project. The particular build that is used will be the build life the 
'resolve' workflow is run from. You'll run these from the Run Workflow 
tab on the build life overview. That will provide the traceability as to 
how the artifact was created and then how it was used in a single place.

Regards,

Eric

Colfer, Brian wrote:
> I like this idea...
>
> To use Artifacts ... 
> 1) I define an artifact set and group in the Admin
> 2) I define the particular path to the artifacts in the Artifact tab for
> the work flow.   I presume that I can use something like:
>
> MT_${bsh:StampLookup.getLatestStampValue()}.tgz 
> CMI_${bsh:StampLookup.getLatestStampValue()}.tgz
>
> to define the particular objects I want make an artifact? 
>
> 3) ... OK now I have to look up the options for resolve artifact ... how
> do I specify the particular build in this step?
>
> Thanks 
> -----Original Message-----
> From: anthill-pro-bounces at lists.urbancode.com
> [mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Eric
> Minick
> Sent: Friday, June 08, 2007 7:44 AM
> To: anthill-pro at lists.urbancode.com
> Subject: Re: [Anthill-pro] Deployment and Artifacts
>
> Brian,
>
> That's what artifacts are for. Let me lay down the standard AnthillPro 
> deployment approach in your format.
>
> 1) Compile jar, war or exe
> 2) Optionally package into a tar with standard name
> 3) Deliver the package (or just all the pieces) as AnthillPro artifacts 
> to be stored centrally.
> 4) Notify the Ops team that build 123 is ready
> 5) Ops team runs deployment workflow to move resolve artifacts to 
> different host, and hopefully automatically deploy. At very least, it 
> will move the files to the staging area for the Ops team to deploy.
>
> What you describe is a hybrid of the standard AnthillPro model and your 
> existing model. I think it's worth considering that this might not be 
> ideal, but if it is what you want it should be quite doable. I would 
> just publish the artifacts to Anthill at build time rather than at 
> deployment time for tighter traceability.
>
> -- Eric
>
> Colfer, Brian wrote:
>   
>> 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 <mailto:briancolfer at yahoo.com>
>>
>> **Skype**: bcolferwork
>>
>> *Shopping.com (tm)
>> **Find. Compare. Buy.**
>> ***www.shopping.com** <http://www.shopping.com/>
>>
>>
>>     
> ------------------------------------------------------------------------
>   
>> _______________________________________________
>> 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
>
>