Skip to content

Commit 5c526d0

Browse files
committed
revert exclude SSIS IR feature
1 parent 618f8b7 commit 5c526d0

File tree

1 file changed

+0
-20
lines changed

1 file changed

+0
-20
lines changed

articles/data-factory/continuous-integration-deployment.md

Lines changed: 0 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -565,26 +565,6 @@ Remember to add the Data Factory scripts in your CI/CD pipeline before and after
565565

566566
If you don't have Git configured, you can access the linked templates via **Export ARM Template** in the **ARM Template** list.
567567

568-
## Exclude Azure-SSIS integration runtimes from CI/CD
569-
570-
If your development factory has Azure-SSIS integration runtime, you can exclude all Azure-SSIS Integration runtimes from CI/CD process in below scenario:
571-
572-
- Azure-SSIS IR infrastructure is complex, and varies in each environment.
573-
- Azure-SSIS IR is set up manually for each environment with the same name. Otherwise publish will fail if there is activity depending on Azure-SSIS IR.
574-
575-
To exclude Azure-SSIS integration runtime:
576-
577-
1. Add a publish_config.json file to the root folder in the collaboration branch, if not exists.
578-
1. Add below setting to publish_config.json:
579-
580-
```json
581-
{
582-
" excludeIRs": "true"
583-
}
584-
```
585-
586-
When publishing from the collaboration branch, Azure-SSIS integration runtimes will be excluded from the Resource Manager template generated.
587-
588568
## Hotfix production branch
589569

590570
If you deploy a factory to production and realize there's a bug that needs to be fixed right away, but you can't deploy the current collaboration branch, you might need to deploy a hotfix. This approach is as known as quick-fix engineering or QFE.

0 commit comments

Comments
 (0)