[Anthill-pro] Anthill3 Preview11

[Eric Minick]

Patrick,

The method I described (a paramaterized tag value, and a parameter in 
the workflow) should work for this.

That said, you might want to look at Anthill's dependency system. Using 
it, you would tell Anthill about the jar files you want saved, and after 
the build it would zip them up and store them internally. Later, you 
could come back to a build life you want to deploy, go to the workflows 
tab, and run the 'deploy' workflow on that build life. The deploy 
workflow would be configured to get the jar files from the artifact 
store and provide them to the workflow. This is the technique we use 
internally to deploy new copies of Anthill Pro 3 to test servers.

-- Eric

Curley, Patrick wrote:

>Let me explain further.  I have a java project in CVS called nibclient,
>I have a project set up in anthill to build this (nibclient-build), it
>also takes the needed jar files and puts then in a zip file, this zip
>file is committed to CVS in a different area than the original java
>project.  Then the zip file is tagged like this: PROD_1_16_0.  
>
>Now I have another project to deploy the nibclient project
>(nibclient-deploy). I want the user to enter the tag as a parameter, so
>they would enter PROD_1_16_0, then anthill3 would check the zip file out
>of cvs using the entered tag.
>
>So I will never check a project out of head if I am doing a deployment.
>
>I just want to pass this parameter to the source config where you setup
>a module.  
>
>Is this possible?
>
>Pat
>
>
>  
>
>-----Original Message-----
>From: anthill-pro-bounces at caladin.urbancode.com
>[mailto:anthill-pro-bounces at caladin.urbancode.com] On Behalf Of Eric
>Minick
>Sent: Thursday, September 21, 2006 11:39 AM
>To: anthill-pro at caladin.urbancode.com
>Subject: Re: [Anthill-pro] Anthill3 Preview11
>
>Patrick,
>
>You will want to create a seperate workflow for building from a tag than
>
>you use for building from head. Presumably, when you build from a tag 
>you will probably not want to relabel, your versioning / stamping will 
>be different, and the source configuration will change a little bit.
>
>So create a seperate source configuration and have the tag field set as 
>${property:tag} .  Then in your workflow, you can either use the same 
>build job as before or create a similar one that has settings more 
>appropriate to building from a tag. In the workflow configuration, you 
>can add properties. The name of one of these properties should be 'tag' 
>and should be required. Then whenever he goes to run the 'Build from 
>tag' workflow, it will prompt the operator for that tag.
>
>I hope that made some sense.
>
>Cheers,
>Eric
>
>Curley, Patrick wrote:
>
>  
>
>>In the source config where you setup a module to checkout of CVS, 
>>their is a text box labeled* Tag**;* is there a way to pass this value
>>    
>>
>
>  
>
>>in as a parameter?
>>
>>What I am trying to do is have the operator who is going to kick off a
>>    
>>
>
>  
>
>>manual build enter the tag and check out the correct code for
>>    
>>
>deployment.
>  
>
>>Pat Curley
>>
>>-----------------------------------------------------------------------
>>    
>>
>-
>  
>
>>_______________________________________________
>>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
>  
>