We recently switched from 1.6 to 2.6.5, and this project is timing out as shown below. We managed to fix in 1.6 but I am the new owner of this system. I managed to pass the “–deploymenttimeout=01:10:00” to octo.exe but it does not seem to be taking effect.
[16:02:58][Octopus Deploy] Running command: octo.exe deploy-release --server http://builder:86 --apikey SECRET --project KK.Intranet.Reports --enableservicemessages --version 1.1.579 --deployto Corporate Pre-Production --progress --deploymenttimeout=01:10:00
[16:02:58][Octopus Deploy] Deploying Octopus Deploy release
[16:02:59][Octopus Deploy] Octopus Deploy Command Line Tool, version 2.5.3.33
[16:02:59][Octopus Deploy]
[16:02:59][Octopus Deploy] Handshaking with Octopus server: http://builder:86
[16:02:59][Octopus Deploy] Handshake successful. Octopus version: 2.6.5.1010; API version: 3.0.0
[16:02:59][Octopus Deploy] Finding project: KK.Intranet.Reports
[16:02:59][Octopus Deploy] Finding release: 1.1.579
[16:03:00][Octopus Deploy] Deploying KK.Intranet.Reports 1.1.579 to: Corporate Pre-Production (Guided Failure: Not Enabled)
[16:03:00][Octopus Deploy] Waiting for 1 deployment(s) to complete…
[16:03:10][Octopus Deploy] Success: Acquire packages
[16:03:11][Octopus Deploy] Success: Step 1: Deploy BozzutosOrders Reports
[16:13:06][Octopus Deploy] One or more tasks did not complete before the timeout was reached. We waited 10.1 minutes for the tasks to complete.
[16:13:06][Octopus Deploy] One or more tasks did not complete before the timeout was reached. We waited 10.1 minutes for the tasks to complete.
[16:13:06][Octopus Deploy] Exit code: -1
[16:13:06][Octopus Deploy] Octo.exe exit code: -1
[16:13:06][Step 1/1] Unable to create or deploy release. Please check the build log for details on the error.
[16:13:06][Step 1/1] Step Octopus Deploy: Deploy Release (OctopusDeploy: Deploy release) failed
This is actually a bug in an old version of Octo.exe which is bundled with the TeamCity plugin. As it happens we had not heard about this at all from anybody until this week, now you’re the second report!
The last time we communicated I got a patch to deal with being stuck with 10 minute timeouts. Now that the project has grown quite a bit, the deployment is taking about 1 hour and 16 minutes to complete (from 10:43am to 11:59am).
I set the timeout to 02:00:00 to give a long timeout of 2 hours, but the timeout is tripping after 70 minutes every time as shown in the log fragment below.
Is there a 70 minute limit baked into the code?
[10:43:18][Octopus Deploy] Running command: octo.exe deploy-release --server http://builder:86 --apikey SECRET --project KK.Intranet.Reports --enableservicemessages --version 1.1.769 --deployto Corporate QA --progress --deploymenttimeout=02:00:00
[10:43:18][Octopus Deploy] Deploying Octopus Deploy release
[10:43:18][Octopus Deploy] Octopus Deploy Command Line Tool, version 2.6.3.60
…
[11:53:18][Octopus Deploy] The build KK.Intranet.Reports::3) Deploy to QA #1.1.769 {buildId=167081} has been running for more than 70 minutes. Terminating…
The build KK.Intranet.Reports::3) Deploy to QA #1.1.769 {buildId=167081}
I think it is TeamCity that decided to terminate the build (‘build’ and ‘buildId’ are TeamCity concepts) - you’ll need to increase the TeamCity build timeout too. Hope this helps!