Note: This is the migration API reference for FAKE 5. The new (modularized) API documentation can be found
here.
If the API is already migrated you can check here if exists in a module.
More information regarding the migration can be found here
TeamFoundation
native support for Azure DevOps (previously VSTS) / Team Foundation Server specific APIs. The general documentation on how to use CI server integration can be found here
Secret Variables
This CI server supports the concept of secret variables and uses the Vault to store them. In order to access secret variables you need to use one of the fake 5 tasks from vsts-fsharp.
Example implementation (supports runner and vault tasks)
1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: |
|
val vault : obj
union case Option.Some: Value: 'T -> Option<'T>
val v : obj
union case Option.None: Option<'T>
val getVarOrDefault : name:'a -> 'b
val name : 'a
val v : 'b
Nested types and modules
Type | Description |
BuildReason | |
Environment |
Functions and values
Function or value | Description |
TeamFoundation.defaultTraceListener
Signature: ITraceListener
|
|
TeamFoundation.detect()
Signature: unit -> bool
|
|
TeamFoundation.install(force)
Signature: force:bool -> unit
|
|
TeamFoundation.Installer
Signature: BuildServerInstaller
|
|
TeamFoundation.logIssue(...)
Signature: isWarning:bool -> sourcePath:string option -> lineNumber:string option -> columnNumber:string option -> code:string option -> message:string -> unit
|
|
TeamFoundation.setBuildState(...)
Signature: state:string -> message:string -> unit
|
|
TeamFoundation.setLogDetailProgress(...)
Signature: id:Guid -> progress:int -> unit
|
|
TeamFoundation.setVariable(...)
Signature: variableName:string -> value:string -> unit
|
|
TeamFoundation.variables
Signature: Vault
|
Access (secret) build variables |
TeamFoundation.write(...)
Signature: action:string -> properties:seq<string * string> -> message:string -> unit
|