Moved processing out of the deployment

Processing is done after deployment because of the invalid JSON that is created by the deployment wizard
avdbrink · Mar 13, 2019 · f9d3033 · f9d3033
1 parent 2e82ad4
commit f9d3033
Show file tree

Hide file tree

Showing 4 changed files with 38 additions and 5 deletions.
diff --git a/BuildSSASTask/task.json b/BuildSSASTask/task.json
@@ -17,7 +17,7 @@
   "version": {
     "Major": 1,
     "Minor": 0,
-    "Patch": 1
+    "Patch": 2
   },
   "demands": [ ],
   "minimumAgentVersion": "1.95.0",

diff --git a/DeploySSASTask/DeploySSASTask.ps1 b/DeploySSASTask/DeploySSASTask.ps1
@@ -135,7 +135,7 @@ try {
 	$xml = [xml](Get-Content $DeploymentOptions)
 	$xml.Data.Course.Subject
 	$node = $xml.DeploymentOptions
-	$node.ProcessingOption = $ProcessingOption
+	$node.ProcessingOption = "DoNotProcess" # Never use anything else or it will break. Porcessing is handled after deployment 
 	$node.TransactionalDeployment = $TransactionalDeployment
 	$node.PartitionDeployment = $PartitionDeployment
 	$node.RoleDeployment = $RoleDeployment
@@ -254,6 +254,37 @@ try {
 		$xml.return.root.Messages.Error | % { Write-Host ($_.ErrorCode + ": " + $_.Description) }
 		Write-Error (Get-VstsLocString -key ErrorDuringDeployment)
 	}
+
+	if ($ProcessingOption -ne "DoNotProcess") {
+		Write-Host (Get-VstsLocString -Key ProcessingDatabase0 -ArgumentList $ProcessingOption)
+
+		# Determine the desired processing option and translate to the correct command for the json we're going to generate
+		if ($ProcessingOption -eq "Full") {
+			$type = "full"
+		} else {
+			$type = "automatic"
+		}
+		# Create a JSON  file containing the processing command
+		$fileContent = @"
+{
+  "refresh": {
+    "type": "$type",
+    "objects": [
+      {
+        "database": "$DatabaseName"
+      }
+    ]
+  }
+}
+"@
+		Set-Content -Path $path\processing.json -Value ($fileContent)
+		Invoke-ASCmd -InputFile $path\processing.json -Server $ServerName | Out-File $path\ProcessingResult.xml
+		$xml = [xml](Get-Content $path\ProcessingResult.xml)
+		if ($xml.return.root.Messages.Error) {
+			$xml.return.root.Messages.Error | % { Write-Host ($_.ErrorCode + ": " + $_.Description) }
+			Write-Error (Get-VstsLocString -key ErrorDuringProcessing)
+		}
+	}
 
 } catch {
     Write-Error (Get-VstsLocString -Key InternalError0 -ArgumentList $_.Exception.Message)

diff --git a/DeploySSASTask/task.json b/DeploySSASTask/task.json
@@ -17,7 +17,7 @@
     "version": {
         "Major": 1,
         "Minor": 0,
-        "Patch": 1
+        "Patch": 2
     },
     "demands": [],
     "minimumAgentVersion": "1.95.0",
@@ -193,9 +193,11 @@
         "AsDBFile0AccessDenied": "Cannot access asdatabase file path: {0}",
         "AsDBFile0": "Asdatabase file path: {0}",
         "CreatingXmlFromAsDatabase": "Creating .xmla file from .asdatabase...",
-        "DeployingDatabase0": "Deploying {0} database ...",
+        "DeployingDatabase0": "Deploying database {0} ...",
+		"ProcessingDatabase0": "Processing the database with processing option {0} ...",
         "Database0DeploySuccess": "{0} database has been deployed successfully",
         "ErrorDuringDeployment":  "Error(s) occurred while deploying database! See above error codes for details",
+        "ErrorDuringProcessing":  "Error(s) occurred while processing database! See above error codes for details",
         "InternalError0": "Task_InternalError {0}",
         "EndingTask": "Ending DeploySSASTask"
     }

diff --git a/vss-extension.json b/vss-extension.json
@@ -1,7 +1,7 @@
 {
     "manifestVersion": 1,
     "id": "VSTS-SSAS",
-    "version": "1.0.1",
+    "version": "1.0.2",
     "name": "SSAS Build & Deploy",
     "scopes": [ "vso.work", "vso.work_write" ],
     "description": "Extension with Continuous Integration support for SSAS",