buildr-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Boisvert <boisv...@intalio.com>
Subject Re: Setting BUILDR_ENV in buildfile has no effect on chosen settings.profile
Date Mon, 23 Feb 2009 02:47:40 GMT
This looks like an issue that was fixed since 1.3.3.

(in order words, it works for me with the current trunk but doesn't with
1.3.3)

alex


On Sun, Feb 22, 2009 at 2:00 PM, Martin Grotzke <
martin.grotzke@javakaffee.de> wrote:

> Hi,
>
> the documentation [1] says
>
>  "You can also set environment variables from within your Buildfile.
>  [..] Make sure to set any environment variables at the very top of
>  the Buildfile, above any Ruby statement (even require)."
>
>
> I tried this with adding
>
>  ENV['BUILDR_ENV'] = 'test'
>
> to the top of my buildfile to set the default profile to 'test'.
> Unfortunately, still the 'development' profile is used (it's printed in
> the very first line after running buildr and I see the 'development'
> profile is applied).
>
> Should setting the 'BUILDR_ENV' variable in the buildfile work, or is it
> just a documentation issue (because it's not meant to work for the
> environment environment variable)?
>
> Btw, what I really want to do: we're using profiles for our development
> machines, with a profile for each machine/hostname, inheriting a common
> profile (like development). Therefore I'd like to initialize the buildr
> environment with s.th. like
>
>  ENV['BUILDR_ENV'] ||= ENV['HOSTNAME']
>
> This just if you wonder why the hell I want to set the default profile
> to 'test' ;)
>
> Thanx && cheers,
> Martin
>
>
> [1] http://buildr.apache.org/settings_profiles.html#environment_variables
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message