Is -e for setting environment variables still required?

[stmax82]

The -e switch for passing variables to the fake build script seems to be broken in fake 5.0.0-rc004. It works fine with 5.0.0-beta029.

The following script reads and prints the variable "foo":

#r "paket:
nuget Fake.Core.Target //"
#load "./.fake/build.fsx/intellisense.fsx"

open Fake.Core

open Environment

Target.create "Build" (fun _ ->
  let foo = environVarOrFail "foo"

  Trace.logfn "foo: %s" foo
)

Target.runOrDefault "Build"

Running fake build -e foo 42 results in the error "Environment variable 'foo' not found":

---------------------------------------------------------------------
Build Time Report
---------------------------------------------------------------------
Target     Duration
------     --------
Build      00:00:00.0005086   (Environment variable 'foo' not found)
Total:     00:00:00.0321655
Status:    Failure
---------------------------------------------------------------------
-> BuildFailedException: Target 'Build' failed.
-> One or more errors occurred. (Environment variable 'foo' not found)
-> Environment variable 'foo' not found

Install fake 5.0.0-beta029 and it works, fake 5.0.0-rc004 doesn't work.

Tested on Win 10 x64.

[matthid]

Sorry, yes this was kind of broken on purpose (more or less).
I'm not sure if this should be removed or kept. Did you look into the new feature of providing arguments to the build script natively:

• https://fake.build/core-commandlineparsing.html (I just noticed that this is probably a bit too hard to find ;) )
• https://fake.build/fake-commandline.html
• https://fake.build/core-targets.html