Closed uchitha closed 5 years ago
I have used an (older) feature to dissable timout, and you can use the Timeout under Control Options for making the task time out.
I am closing this issue. Please reopen if your intended use case is different.
Hi, I am also suffering the timeout. Sometimes my scripts need more than 30 seconds to finish. @johanclasson you said: "I have used an (older) feature to disable timout". Is it released?
If I have understood well, the dbup task will not finish by timeout anymore. Am I wrong?
thanks!
DbUp will not timeout, see this line for how it is implemented.
My guess is that you might be suffering from that something else times out. Have you set a timeout on the Control Options -> Timeout?
To verify, I just ran this SQL-file against a Azure SQL DB using version 2.1.4 of the task, and it did not timeout.
Thanks! Let me check whether I am using the proper task version
Yes, I was using task v1. Now with v2 its working fine, sorry for the incovenience
Nice! Hopefully this can help someone else. I am glad I could be of help!
DB up migrations by default run with a 30 second timeout. This might not be sufficient sometimes. However db up API provides a nice way to configure this.
var upgrader = DeployChanges.To.SqlDatabase(connectionString) .WithExecutionTimeout(TimeSpan.FromSeconds(180)).Build();
Would be useful to surface this up as a setting on the task.
Thank You.