Skip to content

Update ssis-devops-overview.md - SSISDeploy doesn't create #10117

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: live
Choose a base branch
from

Conversation

aligneddev
Copy link

For all my attempts, the SSISDeploy@1 Task doesn't create a new package.
The step is successful in my ADO pipeline, but it is not created.

- task: SSISDeploy@1
              inputs:
                # Example: your build stage artifact from ssisBuild.yml
                # The auto download artifacts puts it in
                sourcePath: '$(Pipeline.Workspace)/${{ parameters.artifactName }}/${{ parameters.environmentName }}/${{ parameters.artifactName }}.ispac'
                # Example: 'SSISDB' or 'File System'
                destinationType: 'SSISDB'
                destinationServer: ${{ parameters.databaseServer }}
                destinationPath: ${{ parameters.destinationPath }}
                authType: 'win'
                whetherOverwrite: true
                whetherContinue: false

If I run SSISDeploy.exe directly, it creates it for me.
SSISDeploy.exe -s:Example.ispac -d:"catalog;/SSISDB/ExampleA;databaseOne" -at:win

Please correct me if I'm wrong.

Copy link
Contributor

@aligneddev : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit f760885:

✅ Validation status: passed

File Status Preview URL Details
docs/integration-services/devops/ssis-devops-overview.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards
Copy link
Contributor

@chugugrace

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Jun 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants