[Anthill-pro] Re: Is it possible (AnthillPro 2.6) to pass a variable to a Build Deployment Manager

Aleph1 Aleph0 alephenne at hotmail.com
Thu Oct 18 08:27:41 CDT 2007


Following Varban and Eric replies, I am indeed planning on maintaining an external collection of old build artifacts (limited to the last N versions, for example).
 
I also understand that the deployment build works with the latest build in teh refernce track.  My problem is simply of passing a variable containing the desired release 
to the deployment builder script.  The script would the do the rest (navigate the external collection and deploy the appropriate release)
   
As I mentioned, I didn't find variables corresponding to the two fields present in the Deployment Build Window ( < Build as Version > and < Next Version > ) in the variables passed to the script.  
 
I found entries in the archives of March 2006 " Build Number for publishing " that point to a way of passing additional properties to a builder through the Build Property provider Scripts.
But (1) I am not sure if it would work with a deployment builder and (2) I don't know, how I could get the user to enter the value.   Is there any way in beanshell script or groovy to ask a
question to the user and save the value as an environment variable or a property?  
 
I understand that Anthill 3 would probably address this issue very nicely but we have no plan to upgrade right now (the licensing model based on number of programmers is not ideal for us, although I understand the rationale behind it).
 
Thanks again for any suggestion -- if there are still 2.X users in the field! ;-).     
 
Eric Mick wrote: 
> Unless you are maintaining an external collection of old build > artifacts, or walking the intranet cleverly, Anthill 2.6 doesn't provide > real support for deploying old versions. AnthillPro3 ALA is really > focused on accomplishing exactly that task.> We knew Anthill 2.6 wasn't architected to solve that problem, and it was > important. So deploying previous builds was a core focus as we set out > to rewrite the application for 3.x.> -- Eric
Varban wrote:
> Please keep in mind that the deployment build manager works only with > the latest build in the referenced build track.Aleph1 Aleph0 wrote:> We are users of AnthillPro 2.6 and I am trying to find a way to pass a > variable to a Build Deployment Manager.>  > The Deployment build screen contains only the following two fields :>                 < Build as Version >> and           < Next Version >>  > but I don't see these variables being passed to the ant script.  There > is an anthill.version variable that is passed, but I believe it id the > version of the base track that the deployment refers to. >  > Does anybody know if either> 1. these two variables are somehow accessible in a build deployment > manager> 2. there is any way to ask the user for a variable (bean shell script > or other?)> 3. any other way to pass a release number (different from the one of > the reference track). >  > What I am trying to do is to allow redeployment of a previous version > of a project, without having to rebuild anything.   >  > Thanks in advance for any tips. >  > Gabriel
_________________________________________________________________
Envoie un sourire, fais rire, amuse-toi! Employez-le maintenant!
http://www.emoticonesgratuites.ca/?icid=EMFRCA120
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20071018/bb4d79df/attachment.htm


More information about the Anthill-pro mailing list