[Anthill-pro] Passing the build stamp via an environment var

[Peter Steele]

Our product backup/upgrade subsystem builds a manifest file during the
build process, and one of the items included in the manifest file is the
build version. So we need to pass the build stamp to this build step for
use when it generates the manifest file. Other build steps will
reference this value as well. I was looking for a way to have this
environment variable set globally, for all build steps. Do you recommend
a difference approach than using an environment variable? 

 

From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Steve
Boone
Sent: Thursday, May 01, 2008 10:52 AM
To: AnthillPro user and support list.
Subject: Re: [Anthill-pro] Passing the build stamp via an environment
var

 

On the project level, you could create an environment variable. 

Then, you would need to create a script that took the current Stamp
Value, and saved it to the Environment Variable you created.  

What do you want to do with the environment variable after you have it
set? 

On Thu, May 1, 2008 at 1:37 PM, Peter Steele <psteele at maxiscale.com>
wrote:

I want to configure our builds to set an environment variable to be
equal to the build stamp for the given build. Is there a way to do this
that would work across all steps of a build job or do I need to set the
environment variable separately for each build step?

 


_______________________________________________
Anthill-pro mailing list
Anthill-pro at lists.urbancode.com
http://lists.urbancode.com/mailman/listinfo/anthill-pro

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20080501/1094c391/attachment-0001.htm