ah ok. I am not sure I understood what is the build environment documentation you are referring to. Pls send a link. Or are you referring to the build definition templates?
Murali. On Fri, Nov 7, 2008 at 2:17 PM, Kyle Lebel <[EMAIL PROTECTED]> wrote: > Yes this setup makes sense. We could do that. > > I just read the build environments doc and was wondering if it's something > we could control at a higher level, instead of having to add build args to > each build. Say - every project we would automate should contain a > "continuum" profile. On continuum, wed define this build environment once > and select it from the drop down in the build definition. I guess I'm > trying to understand what those build environments are for... > > Kyle > > ________________________________ > > From: murali mohan [mailto:[EMAIL PROTECTED] > Sent: Fri 11/7/2008 9:10 AM > To: [email protected] > Subject: Re: Build Environments > > > > I have a similar setup in continuum. > > The profile definition: > <profile> > <id>sampleProfile</id> > > <activation> > <activeByDefault>false</activeByDefault> > <property> > <name>live-tests-only</name> > </property> > </activation> > > This profile can be activated either by passing the arguments > "-PsampleProfile" or "-Dlive-tests-only". You can pass these argument to > the > continuum builds by adding these in the arguments section when you define a > build. > > Murali. > > On Fri, Nov 7, 2008 at 1:58 PM, Kyle Lebel <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > I have a question regarding the Build Environments. What I am trying to > do > > is activate a profile when building from continuum. I would like to do > this > > using an environment variable somehow. But reading the Build > Environments > > documentation, it seems to indicate I could create this environment > variable > > through here - and have my builds using that build environment. Is this > > correct, or have I misunderstood something? > > > > Kyle > > > > >
