One of my developers has a long running Octopus Deploy step that is timing out after 10 minutes. The step will take more than 10 minutes (creating clustered index on very large dataset). Is there a way I can tell Octopus to increase the timeout on that step (or overall)?
I tried to find a similar support issue, but it seems most of the support issues involve calling the Octo plugin from TeamCity or VSTS. This is pure Octopus Deploy here.
Here’s the log…
15:08:01 Info | --------------------------END RAW SQL SCRIPT----------------------------
15:08:01 Info | Script Output: Changed database context to ‘CUSTOMDB’.
15:18:03 Info | ERROR:
15:18:03 Info | An exception occurred while executing a Transact-SQL statement or batch.
15:18:03 Info | Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding… LineNumber: 0
15:18:03 Info | The statement has been terminated… LineNumber: 1
15:18:09 Error | Command failed with exit code 200
15:18:09 Error | At
15:18:09 Error | E:\Octopus\Applications\PAYER_INT\IN_MED_MPL_DB\1.0.0.202372_2\Bootstrap.Octopus.Action.CustomScripts.Deploy.ps1:3436
15:18:09 Error | char:9
15:18:09 Error | + throw "Command failed with exit code $($LastExitCode)"
15:18:09 Error | + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15:18:09 Error | + CategoryInfo : OperationStopped: (Command failed with exit code 200:String) [], RuntimeException
15:18:09 Error | + FullyQualifiedErrorId : Command failed with exit code 200
15:18:09 Error | Deploy script returned non-zero exit code: 1
15:18:09 Error | Running rollback conventions…
15:18:09 Verbose | Adding journal entry:
15:18:09 Verbose |
15:18:09 Error | Deploy script returned non-zero exit code: 1
15:18:09 Verbose | Updating manifest with output variables
15:18:09 Verbose | Updating manifest with action evaluated variables
15:18:09 Verbose | Planning retention policy
15:18:09 Fatal | The remote script failed with exit code 1
15:18:09 Verbose | at Octopus.Worker.Scripting.ScriptResult.EnsureSuccessful() in Z:\buildAgent\workDir\eec88466c176b607\source\Octopus.Worker\Scripting\ScriptResult.cs:line 91
| at Octopus.Server.Orchestration.Deploy.Guidance.Execute(Action callback) in Z:\buildAgent\workDir\eec88466c176b607\source\Octopus.Server\Orchestration\Deploy\Guidance.cs:line 59
| at Octopus.Server.Orchestration.Deploy.DeploymentTaskController.<>c__DisplayClass28_0.b__0() in Z:\buildAgent\workDir\eec88466c176b607\source\Octopus.Server\Orchestration\Deploy\DeploymentTaskController.cs:line 324
| at Octopus.Server.Orchestration.Deploy.DeploymentTaskController.ExecuteWithTransientErrorDetection(Action action, Machine machine) in Z:\buildAgent\workDir\eec88466c176b607\source\Octopus.Server\Orchestration\Deploy\DeploymentTaskController.cs:line 428
| at Octopus.Server.Orchestration.Deploy.DeploymentTaskController.ExecuteActionAndInitLoggingContext(PlannedStep step, Machine machine, PlannedAction action) in Z:\buildAgent\workDir\eec88466c176b607\source\Octopus.Server\Orchestration\Deploy\DeploymentTaskController.cs:line 321
15:18:09 Fatal | Deploy database on DAYINTPTSDEP01