[Anthill-pro] Anthill3-rc2

[Curley, Patrick]

Eric,

Your other approaches will not quite work for us.  We have a different
operator for builds and deploys.  The builder has to be the one who
enters these properties.  I am also using these values in CVS for
branching and tagging.

Here is our scenario:  Every month we have a code release for the Fred
system.  We know ahead of time what the release number will be.  This
month it was Release_1_16_0, next month it will be Release_1_17_0, if
there is a bug fix between major releases it will be Release_1_16_1 or
Release_1_17_1.

So, when we do the build via Anthill3 it goes like this: The operator
selects the Release workflow (rather than the dev workflow), anything in
one of the Fred CVS modules tagged with PROD_RELEASE will be checked out
of CVS.
Operator is prompted for two properties; BRANCH and RELEASE; operator
fills in this info; RELEASE is 1_16_0, BRANCH is Release_1_16_0.  Now
Anthill3 does the rest of the build and all works fine. 

Now one of the non-originating workflows is being used to deploy the
artifacts built from the originating workflow.
So, the operator selects the appropriate buildlife and goes to the run
workflow tab and from the dropdown selects Client-Deploy, then he clicks
build. NOTE: I do not want to prompt the operator for RELEASE as part of
the non-originating workflow.

I want to use the value of RELEASE in my deploy ant script for logging
and also in my deploy notification (Email).



I hope this explanation helps,

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: Tuesday, October 17, 2006 10:50 AM
To: anthill-pro at caladin.urbancode.com
Subject: Re: [Anthill-pro] Anthill3-rc2

Patrick,

I have one of my guys checking for an approach on how to do this. He's 
pretty sure he has it, but needs to set up a quick test. I have a 
feeling you've explained this to me before, but could you remind me what

you use the release value for? Generally, we see people have a lot of 
success postponing assigning a formal build number until they decide to 
run that secondary workflow.

Also, if this is a build number, it might make sense to set up a custom 
stamping template and use that release property to create a stamp. 
Looking up a stamp and passing that to an ant script should be pretty 
straight forward as well.

Do either of those approaches work?

-- Eric

Curley, Patrick wrote:

>
> I have a project named Fred with a property called RELEASE in my 
> originating workflow, I use this in my ant script, and this works 
> fine.  Fred also has a non-originating workflow, I would like to use 
> this same property, RELEASE in this ant script, is this possible?
How?
>
>
>
>
> Thanks,
>
> 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