Forum Discussion
Deploying Warehouse fails
Guys, sorry, but this is the same as all released Fabric features. Nothing is designed well to be linked with the whole Fabric ecosystem. I gave two chances to this feature.... Now (after months) its still not working.
Each part has own team. and nothing works together properly. The current issue is, that if you move warehouse from one workspace to another, it will change the ID. That fine, and its obvious. But somebody who designed warehouse Git integration did not work with this information. So whenever you want to checkout branch from your dev collaborate workspace to your own one. It will fail and you can not merge your changes back again, cause in git, there is no only db project. but some config files with warehouse id. And yea. warehouse in your branch is now no that one in main branch 🙂
To be honest I'm not using deployment pipelines as they're not flexible enough to suit a variety of ci-cd options.
- evrise2 years ago
Advocate II
Thanks AndyDDC , but am not talking about deployment pipelines just now. This is step before, when you want to make cahnges as a developer an merge it back to main branch (CI). Deployment pipelines is the next step (CD).
But if would be so kind, can you describe shortly how do you do CI on your site ? Do you have exported dacpac locally, making changes there and build project within DevOps CI pipelne, or something different ? Thanks a lot for ur time.