Replies: 1 comment
-
In the build step, you need to point out the solution file (.sln) rather than specific or each database project. That's it. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Kamil,
Thank you again for the highly informative video on CICD on youtube. I was able to follow your example and build the automated CICD pipeline for database build and deploy successfully to azure cloud using the AdventureWorks database. My actual system has 6 databases where each database refers to tables on other databases. I am able to build the solution in VS code and that creates 6 dacpac files in each of the individual project folders. The problem is when I try doing the same in Azure DevOps, using the same approach as the example creates just one DACPAC file. I am sure i would need to somehow modify the Azure DevOps build process to build individual dacpacs but I am at a dead end there since I am using the classic YAML as an example. Any guidance will be highly appreciated. Thank you in advance.
Beta Was this translation helpful? Give feedback.
All reactions