Octopus Runner Timeouts

Completed
Avatar
Wdiamond
Created

Have been using TeamCity for a few years and just started getting timeouts on the Octopus Deploy Step.

"[Octopus Deploy] One or more tasks did not complete before the timeout was reached. We waited 00:10:06 for the tasks to complete."

I set Hanging Builds Detection = False and the Failure Conditions is set to 120 minutes

The deploy in Octopus does finish error free, it is just taking a long time. We recently added several new objects to the database and it does take longer now. From what I have read, this can trigger timeouts until TeamCity builds new statistics regarding estimated times. I have run this build configuration a dozen times and it is still happening. I would have thought that disabling hanging detection would have eliminated that.

 

TeamCity Professional 2021.1.2 (build 92869) 

Windows Server 2016

 

 

Any suggestions?

Votes

0

Share

4 comments
Avatar
Wdiamond
Created

It appears the the timeout issue is only in the Octopus Deploy (Step 7), as the Build Database (step4) is taking 26 minutes and is not timing out.

Step Duration
Step 0: Package Start 1
Step 1/8: NuGet Installer (25s) 0
Step 2/8: Build web project (MSBuild) (1m:45s) 1
Step 3/8: Push web package to octopus (OctopusDeploy: Push Packages) (59s) 0
Step 4/8: Build database solution (TOM_Reports) (Visual Studio (sln)) (26m:41s) 26
Step 5/8: Push Database package (TOM_Reports) (OctopusDeploy: Push Packages) (9s) 0
Step 6/8: Deploy Database (OctopusDeploy: Create release) (10m:16s) 10
Step 7/8: Deploy Web (OctopusDeploy: Create release) (2m:07s) 2
Step 8/8: Unit Test WEB (Visual Studio Tests) 0
Total Duration 40
0
Avatar
Mikhail Efremov
Created

Hi,

Judging by your initial message, the problem is that the plugin just cannot detect that some of its actions were finished successfully:

"[Octopus Deploy] One or more tasks did not complete before the timeout was reached. We waited 00:10:06 for the tasks to complete."

JetBrains is not the developer of this plugin, so it may be better to reach out to the plugin's developer directly. 

From what I have read, this can trigger timeouts until TeamCity builds new statistics regarding estimated times. I have run this build configuration a dozen times and it is still happening. I would have thought that disabling hanging detection would have eliminated that.

Does TeamCity actually detect the build as hanging? Could you please provide an example:

  • screenshot of the build overview page
  • build log downloaded from the UI
  • teamcity-agent.log from the corresponding agent.

You can use our uploads service to send us the files, just let me know the upload ID.

0
Avatar
Wdiamond
Created

Mikhail,

I was able to resolve it by updating the plugin from Octopus.

0
Avatar
Mikhail Efremov
Created

Glad to hear that!

0

Please sign in to leave a comment.