You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/synapse-analytics/cicd/continuous-integration-delivery.md
+12-14Lines changed: 12 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -493,45 +493,43 @@ If you're using Git integration with your Azure Synapse workspace and you have a
493
493
494
494
## Troubleshoot artifacts deployment
495
495
496
-
### Publish failed: workspace arm file is more then 20mb
497
-
498
-
There is a file size limitation in git provider, for example, in Azure DevOps the maximum file size is 20Mb. Once the workspace template file size exceeds 20Mb, this error happens when you publish changes in Synapse studio, in which the workspace template file is generated and synced to git. To solve the issue, you can use the Synapse deployment task with **validate** or **validate and deploy** operation to save the workspace template file directly into the pipeline agent and without manual publish in synapse studio.
499
-
500
-
501
496
### Use the Synapse workspace deployment task to deploy Synapse artifacts
502
497
503
-
In Azure Synapse, unlike in Data Factory, artifacts aren't Resource Manager resources. You can't use the ARM template deployment task to deploy Azure Synapse artifacts. Instead, use the Synapse workspace deployment task to deploy the artifacts, and use ARM deployment task for ARM resources (pools and workspace) deployment. Meanwhile this extension only supports Synapse templates where resources have type Microsoft.Synapse
498
+
In Azure Synapse, unlike in Data Factory, artifacts aren't Resource Manager resources. You can't use the ARM template deployment task to deploy Azure Synapse artifacts. Instead, use the Synapse workspace deployment task to deploy the artifacts, and use ARM deployment task for ARM resources (pools and workspace) deployment. Meanwhile this task only supports Synapse templates where resources have type Microsoft.Synapse. And with this task, users can deploy changes from any branches automatically without manual clicking the publish in Synapse studio. The following are some frequently raised issues.
499
+
500
+
#### 1. Publish failed: workspace arm file is more than 20MB
504
501
502
+
There is a file size limitation in git provider, for example, in Azure DevOps the maximum file size is 20Mb. Once the workspace template file size exceeds 20Mb, this error happens when you publish changes in Synapse studio, in which the workspace template file is generated and synced to git. To solve the issue, you can use the Synapse deployment task with **validate** or **validate and deploy** operation to save the workspace template file directly into the pipeline agent and without manual publish in synapse studio.
505
503
506
-
### Unexpected token error in release
504
+
#### 2. Unexpected token error in release
507
505
508
506
If your parameter file has parameter values that aren't escaped, the release pipeline fails to parse the file and generates an `unexpected token` error. We suggest that you override parameters or use Key Vault to retrieve parameter values. You also can use double escape characters to resolve the issue.
509
507
510
-
### Integration runtime deployment failed
508
+
#### 3. Integration runtime deployment failed
511
509
512
510
If you have the workspace template generated from a managed Vnet enabled workspace and try to deploy to a regular workspace or vice versa, this error happens.
513
511
514
-
### Unexpected character encountered while parsing value
512
+
#### 4. Unexpected character encountered while parsing value
515
513
516
514
The template can not be parsed the template file. Try by escaping the back slashes, eg. \\\\Test01\\Test
517
515
518
-
###Failed to fetch workspace info, Not found.
516
+
#### 5. Failed to fetch workspace info, Not found
519
517
520
518
The target workspace info is not correctly configured. Please make sure the service connection which you have created, is scoped to the resource group which has the workspace.
521
519
522
-
###Artifact deletion failed.
520
+
#### 6. Artifact deletion failed
523
521
524
522
The extension will compare the artifacts present in the publish branch with the template and based on the difference it will delete them. Please make sure you are not trying to delete any artifact which is present in publish branch and some other artifact has a reference or dependency on it.
525
523
526
-
### Deployment failed with error: json position 0
524
+
#### 8. Deployment failed with error: json position 0
527
525
528
526
If you were trying to manually update the template, this error would happen. Please make sure that you have not manually edited the template.
529
527
530
-
###The document creation or update failed because of invalid reference.
528
+
#### 9. The document creation or update failed because of invalid reference
531
529
532
530
The artifact in synapse can be referenced by another one. If you have parameterized an attribute which is a referenced in an artifact, please make sure to provide correct and non null value to it
533
531
534
-
### Failed to fetch the deployment status in notebook deployment
532
+
#### 10. Failed to fetch the deployment status in notebook deployment
535
533
536
534
The notebook you are trying to deploy is attached to a spark pool in the workspace template file, while in the deployment the pool does not exist in the target workspace. If you don't parameterize the pool name, please make sure that having the same name for the pools between environments.
0 commit comments