Closed matthid closed 6 years ago
To dogfood this in FAKE I need to add another task in order to only generate the secret variable stuff, this task is probably not very useful to anyone else but FAKE, not sure if we should add it here (it might be useful if you are not using the runner task and still want to access the secret variables)?
I'm quite positive that this is ready, I hope I didn't break the PaketRestore task
Maybe for marketing purposes we should have a separate "fake" extension (to be independent of "F#")? However I'm fine with having everything here in a single repository. What do you think?
@matthid I had the same thought re: FAKE - I'm happy to support either model :-)
And thanks for adding this :-)
Thinking this further: "Paket" is not a "F# helper" either... Maybe we should rename this completely :/
Yeah, it is a bit misleading. Not sure what to rename it to, as it has an F# runner there too.
The good thing about a single extension is that people need to ask their admins only once, while with 3 extensions (Paket, Fake, F#) they might need to ask multiple times :/
And realistically that the tasks are used and installed together makes completely sense to me
Basically a full-featured fake 5 runner task. Even added support for secret & encrypted variables to fake. However secret variables are only usable when a new
Fake.BuildServer.TeamFoundation
package is released (probably soon)Similar to other tasks it will ask the user for a version and download and cache fake. The task currently requires
DotNetCore
to be available (the easiest way is to use theDotNetCoreInstaller
task). We can consider lifting that requirement and download the self-contained package instead (but that was out of scope for the first implementation)I guess docs are still missing