You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Introduction
Currently, in our project, there are around 10+ DB's as part of the same DB solution file because there are references between these DB's. As a result, the build time for the entire DB solution is more than 60mins which is not acceptable in a CI scenario. In order to mitigate this Build Time, our DB automation team has configured the DB project in such a way that all DB objects are excluded and only the DB object which needs change is required to be included by developer say developer1 as part of the DB project which will only have DB changes of that developer1. The developer2 who commits his change after developer1 will not have developer1 changes and can be deployed and independently. Question
Is this the correct approach because as per my understanding a CI build should have all the developers changes as part of the build as it is existing code change in the repo + new change to be checked in by the developer?
Is there any better way to reduce the build time when there are references between the DBs?
Also, the other thing is that PROD release may be on a different day as compared to the check-in day wherein it will make more sense to deploy the latest Release-100 out 100 Releases rather than deploying Release-1To100 on the release day because each developer Build Artifact is different due to exclusion and inclusion.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
DevOpsBharat asked this question on my YouTube channel:
Introduction
Currently, in our project, there are around 10+ DB's as part of the same DB solution file because there are references between these DB's. As a result, the build time for the entire DB solution is more than 60mins which is not acceptable in a CI scenario. In order to mitigate this Build Time, our DB automation team has configured the DB project in such a way that all DB objects are excluded and only the DB object which needs change is required to be included by developer say developer1 as part of the DB project which will only have DB changes of that developer1. The developer2 who commits his change after developer1 will not have developer1 changes and can be deployed and independently.
Question
Is this the correct approach because as per my understanding a CI build should have all the developers changes as part of the build as it is existing code change in the repo + new change to be checked in by the developer?
Is there any better way to reduce the build time when there are references between the DBs?
Also, the other thing is that PROD release may be on a different day as compared to the check-in day wherein it will make more sense to deploy the latest Release-100 out 100 Releases rather than deploying Release-1To100 on the release day because each developer Build Artifact is different due to exclusion and inclusion.
Beta Was this translation helpful? Give feedback.
All reactions