You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@buildr.apache.org by Martin Grotzke <ma...@javakaffee.de> on 2009/02/22 23:00:27 UTC
Setting BUILDR_ENV in buildfile has no effect on chosen
settings.profile
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
Re: Setting BUILDR_ENV in buildfile has no effect on chosen
settings.profile
Posted by Assaf Arkin <ar...@intalio.com>.
On Sun, Feb 22, 2009 at 11:53 PM, Martin Grotzke <
martin.grotzke@javakaffee.de> wrote:
> On Sun, 2009-02-22 at 18:47 -0800, Alex Boisvert wrote:
> > 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)
> Ok. Is there somewhere a step by step guide how to install buildr from
> trunk (I didn't find this)?
rake install
or sudo rake install
Assaf
>
>
> Is 1.3.4 planned already?
>
> Cheers,
> Martin
>
> >
> > 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
> > >
> > >
>
Re: Setting BUILDR_ENV in buildfile has no effect on chosen
settings.profile
Posted by Martin Grotzke <ma...@javakaffee.de>.
On Sun, 2009-02-22 at 18:47 -0800, Alex Boisvert wrote:
> 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)
Ok. Is there somewhere a step by step guide how to install buildr from
trunk (I didn't find this)?
Is 1.3.4 planned already?
Cheers,
Martin
>
> 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
> >
> >
Re: Setting BUILDR_ENV in buildfile has no effect on chosen
settings.profile
Posted by Alex Boisvert <bo...@intalio.com>.
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
>
>
Re: Setting BUILDR_ENV in buildfile has no effect on chosen
settings.profile
Posted by Martin Grotzke <ma...@javakaffee.de>.
On Mon, 2009-02-23 at 00:23 -0800, Assaf Arkin wrote:
> 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)?
>
>
> Not supposed to work for BUILDR_ENV. This environment variable is used
> before the buildfile is loaded.
Ok, thanx for the info.
Cheers,
Martin
>
> http://buildr.apache.org/settings_profiles.html#environments
>
> It shows the two supported ways for setting the environment. You might have
> to wrap Buildr with another script that does something like:
>
> buildr -e $HOSTNAME
>
> Assaf
>
>
> >
> >
> > 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
> >
> >
Re: Setting BUILDR_ENV in buildfile has no effect on chosen
settings.profile
Posted by Assaf Arkin <ar...@intalio.com>.
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)?
Not supposed to work for BUILDR_ENV. This environment variable is used
before the buildfile is loaded.
http://buildr.apache.org/settings_profiles.html#environments
It shows the two supported ways for setting the environment. You might have
to wrap Buildr with another script that does something like:
buildr -e $HOSTNAME
Assaf
>
>
> 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
>
>