I have been creating a lot of Build Tasks for the new TFS 2015 Build and Release.
I have discovered a few tricks that were not simple to find. I thought I would Blog about them for my own record and anyone who happens by.
This Blog post makes the assumption that you have already been creating your own build tasks. If not, and you want some background take a look here first.
In this example I created a Release task to perform a DACPAC deployment. The script calls SQLPackage.exe which can do several things. Deploy the changes directly to a Database or generate a Deployment Report, a Drift Report or the SQL that needs to be run to update the target, amongst others.
So I figured I would make my Build Task smart enough to let the end user select which action they would they would like to perform. To do that I need the user to select which action and have that passed into my Powershell script.
The input value that is defined in my task.json file looks like this.
"helpMarkDown": "Select the Action to perform",
"Publish": "Publish Changes",
"Script": "Script Changes",
"DeployReport": "Generate Deployment Report"
The type needs to be “picklist”. I also needed to define options. Each option is comprised of two strings seperated by a semicolon. The string before each semicolon is the value to be returned and the string after the semicolon is the display name. Notice I set one of the values to be the defaultValue.
Once published to TFS the build task inputs will look something like this.
Now the selected value will be passed into my Script and I can change my call to SQLPackage.exe accordingly.