Skip to content
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

DacPac Deploy Task does not log stderr to Build/Release Log #3002

Closed
colindembovsky opened this issue Nov 1, 2016 · 2 comments
Closed

DacPac Deploy Task does not log stderr to Build/Release Log #3002

colindembovsky opened this issue Nov 1, 2016 · 2 comments
Assignees

Comments

@colindembovsky
Copy link
Contributor

When using the DacPac Deploy Task, I can see what looks like stdout in the build/release log. However, if the dacpac deployment fails, the stderr output does not appear in the build/release log. I do see:

Initializing deployment (Start)
Initializing deployment (Failed)

##[error]
ErrorRecord : *** Could not deploy package.

However, running the same command in a console gives the actual error (like incorrect SQL version or whatever). It would be great if the stderr was put onto the build/release logs so that we can see error details.

@nickeyyan
Copy link
Member

@KrishnaAdityaB Since my team has used VSTS to do our deployment and we have many databases. If the deployment failed without detail log, we have to spend a lot of time on investigating. Please fix this issue ASAP. Thanks a lot.

@KrishnaAdityaB
Copy link
Contributor

SQL Server Database Deploy task in this repo is deprecated. Please use the WinRM - SQL Server DB Deployment task from this extension.

This issue has been moved to the new task's repo microsoft/azure-pipelines-extensions#147

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants