Comments
Sort by recent activity
Kendra_Little said:
Hello, Yes, the build process creates a database for validation purposes. If you skip this step, you would lose assurances that the code you have committed is valid SQL that is suitable for a deployment. You have the option to have the build dynamically create the database for this purpose and drop it after, or if it is more convenient you can hardcode a name for the database and reuse an existing database for each build. (The database will be "cleaned" so validation can succeed.) Can you explain why you would like to skip this step? Is there some barrier preventing you from using a database for this purpose, or some problem that you are hitting? Cheers, Kendra
Hi Kendra, Thanks for the explaining but we really hope if we can have an option bypassing it. When deploying, we are using transactions so that if there is an error, we will get it eventually. Make us feel that the extra safeguard is redundant in most of the case. The most important reason for us is time. We have a large DB so every time the build cost 10+ mins, and developers really want them fast pace into our Dev env. We hope that we can have an option so that we can only enable the DB validation when we try to deploy to our Prod, and enjoy your assurance feature when we need [image]
/ comments
Kendra_Little said:
Hello,Yes, the build process creates a database for validation purposes. If you skip this step, you would lose assurances that the code you have committed is valid SQL tha...