Here in the company I'm working for I created the model allowing to us
to be flexible across environments settings.
If in short then:

1. We produce every time only single general artifact and not
environment specific, let's say war file. 
2. Then we need to deploy it on different environments and for this I
created environment configuration file which is descriptor of the
environment. 
3. Environment descriptor contains information about general settings
which belong to this environment, about servers and their settings that
are on this environment and about applications and their settings that
are on these servers. 
4. In the same time every produced artifact contains its own descriptor
and contains for example default values for settings if any. 
5. Another item in this model is the tool I named installer which takes
produced artifact and environment descriptor as a input and produce
customization where as a result you have artifacts specific for the
server on certain environment. If it's required it also can be deployed
using the same application. 

So, we have general artifact as build result with its own component
descriptor, self-explained environment descriptor for each environment
and application which perform actions with the artifacts on specified
environment using provided environment descriptor.

Best regards,
                     Juri.

-----Original Message-----
From: EJ Ciramella [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 03, 2008 9:15 PM
To: [email protected]
Subject: Building for different environments - how do _you_ do it?

So how are other people building for both dev and other environments?

 

For example, how does one support multiple environments like the
following:

 

1 - Dev integration

2 - QA stack 1

3 - QA stack 2

4 - QA stack 3

5 - Staging

6 - Prod

7 - local developer builds

 

How do other people support variables that can be the same from local
builds through production but support the option to change them at the
last minute?  Are people building multiple version of say an ear
deployment to support all the different environments?


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to