DataStar Pipeline Tasks
DataStar Version: 220.127.116.11
DATASTAR is a unique set of development tools to enable you to version database components including data utilizing your existing source control system. With DATASTAR you describe how you want to componentize your data and then use the software to generate scripts which encapsulates this data as components. DATASTAR integrates with your source control system so that you can identify changes and package a deployment accordingly. This repo contains the tasks that are provided out-of-the-box with DataStar to integrate with an Azure DevOps or Team Foundation Server Continuous Integration (CI) and Continuous Delivery (CD) environment.
Add Work Item History
The task is used to add history to a TFS Work Item. The task uses the TFS Web Service API to create the history entry.
See the documentation for Add Work Item History.
The task is used to apply a label to the items contained in a release control file.
See the documentation for Apply Label.
Associate Build With Work Items
The task is used to associate the current build to one or more work items. The task uses the TFS Web Service API to create the association any existing work item association with builds will be removed before the new association is created.
See the documentation for Associate Build With Work Items.
The task is used to execute the Command Line Utility. This can be run one of the following modes:
Deployment - this provides the ability to deploy a packaged build of scripts to a target environment and optionally create the scripts necessary to reverse the changes.
Reversal - the reversal mode will apply the scripts necessary to back out a previous deployment where reversal scripts were generated.
Generate - the generate mode allows you to generate the scripts from a template so that you can automate the extract from an environment.
History - the history mode allows the export scripts and deployment logs that have been persisted in the deployment tables from previous deployments.
See the documentation for DataStar CmdLine.
License: License Key Required: Commercial
For a specified work item, this script will pull the .xml release control files for that work item and create 1 manifest file(.mf) for each .xml file and it will build the appropriate folder structure for the files contained in those scripts. A typical release\deployment file will look like as follows:
See the documentation for DataStar Get Sources.
Set Json Parameters
The task is used to read a Json file and set TFS Variables using the Json properties. For example a Json file with the following format will set variables for "BuildId", "WorkItem", "Version" and "BuildNumber" with their associated values.
See the documentation for Set Json Parameters.
The task is used to apply one or more tags to one or more builds.
See the documentation for Tag Build.
The task is used to update one or more builds using a Json String to set the attributes. For example a Json string with the following format can be used to retain a build indefinitely:
See the documentation for Update Build.
The task is used to write a file containing variables that are resolved when the file is written. Typically this is used to create a Json properties file for example:
Note you can include any variables, in addition a special variable substitution has been added $(REV) which will assign the value to the digits after the last period in the standard build number variable. For example if your build number is "1234.99" then the "$(Rev)" variable will be replaced with "99".