Build Automation "Stopped Hearing From Agent Hosted Agent" Error.

(0) Share

Report

Posted on by HAIRUL HAZRI

1,214

Hi,

My build pipeline failed on "Create Deployable Package" step with following error:

"We stopped hearing from agent Hosted Agent. Verify the agent machine is running and has a healthy network connection. Anything that terminates an agent process, starves it for CPU, or blocks its network access can cause this error. "

Is it because the build takes too long? We set the repository to public, so timeout shouldn't be an issue here, I suppose.

But why does the agent return this error?

Thank you.

I have the same question (0)

All responses (11)

Answers (0)

nmaenpaa 101,160 Moderator on at

Like (0)

Report

With public repository there should be no time limit. But are you sure that you want to publish your ADO project as a public project? Is it agreed with your customer?

The duration of the build step (41 min 55 s) seems very long. Did it always take this long?

Was this reply helpful? Yes No
HAIRUL HAZRI 1,214 on at

Like (0)

Report

Hi Nikolaos,

we have more than 50 models to build. We didn't use version control before, so we create a model for each requirement. Before all-in-one deployable package, we deploy each requirement model by model. So we had no problem with build duration before. We only recently aware that this is not a good practice.

Now that we have so many models, to build the all-in-one package would take this long. We had no choice but to make the repos public to bypass the timeout error somehow.

Was this reply helpful? Yes No
Sergei Minozhenko 23,093 on at

Like (0)

Report

Hi HAIRUL,

You can set up a timeout on the agent job level. Recently I had an issue with 1-hour timeout on agent hosted build and I just increased it to 2 hours. But in my case, I saw an error about the timeout (so I'm not sure if your issue is related to timeout)

Was this reply helpful? Yes No
nmaenpaa 101,160 Moderator on at

Like (0)

Report

By the way, do you get this error on each build? Does it always happen in the same step and/or after the same time?

Was this reply helpful? Yes No
HAIRUL HAZRI 1,214 on at

Like (0)

Report

Hi Sergei,

Create Deployable Package task timeout already set to 0. Should be infinite here:

Also, build timeout is set to 2 hours:

But error received only after 1 hour 14 minutes.

Was this reply helpful? Yes No
HAIRUL HAZRI 1,214 on at

Like (1)

Report

Hi Nikolaos,

not on each build, but more error than successful rates. One thing I noticed, when the build is successful, it took around 58, 59 minutes. That is barely less than an hour.

Its frustrating getting the error only after waiting more than an hour.

Was this reply helpful? Yes No
Sergei Minozhenko 23,093 on at

Like (0)

Report

Hi Hairul,

On your screenshot, I see timeout for the whole build job, but I was talking about agent job timeout ("Compile x++" agent job where all tasks are added)

docs.microsoft.com/.../phases

Was this reply helpful? Yes No
nmaenpaa 101,160 Moderator on at

Like (0)

Report

Perhaps it would anyway be a good idea to try to consolidate the code in fewer models. It would be easier for maintainability in the long run. You're not the only one who has chosen this "one model for each custom functionality" approach - also I was using it initially. And I've seen many others do the same thing. It indeed allowed to deploy customizations in a more granular way, but the correct approach would be instead to have separate dev and main branches, and merge only the "to-be-delivered" changes to main branch for deployment.

The fact that Microsoft itself split the base application in numerous models and packages also indicated that it would make sense to split one's own code as well.

The good news is that it should be quite straight forward to consolidate the code - mostly copy paste of files and/or fields/methods etc.

This is not directly related to your question, just wanted to share my thoughts.

Was this reply helpful? Yes No
HAIRUL HAZRI 1,214 on at

Like (0)

Report

Hi Sergei,

Job timeout is set to 0. Should be able to run up to 6 hours here since the repos is public.

Was this reply helpful? Yes No
HAIRUL HAZRI 1,214 on at

Like (0)

Report

Yes Nikolaos. We are actually thinking to consolidate the code & reduce the number of models so that we can reduce the build time. But maybe in the future. After all, we need to consider deleting those models as well. Plus we have more important projects ongoing at the moment.

For now, we just want to survive the all-in-one package enforcement.

Was this reply helpful? Yes No