nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can I accidentally kill processes from another build?

Victor Rulev

I'm running unit tests after the application is built. They can hang up, so I need to kill the process and fail the build after certain timeout.

I've written a batch file that handles it by using Windows "timeout", "tasklist" and "taskkill" commands. The question is, if two builds are launched simultaneously, is there a chance that one of them would kill the process from another build? And how about "tasklist" command, do separate builds have separate task lists?

Accepted answers

Jimmy Seddon

Hi @Victor Rulev,

Welcome to the Community!

To answer your question directly, yes you can accidentally kill processes of another build if you aren't careful.

I haven't done what you are doing in a batch file, but we spawn a number of background jobs using Powershell for our builds and we are careful to give them specific naming conventions so that if we kill a job do to a timeout threshold being passed, we know that the job being terminated belongs to the build that spawned it.

I hope that help!

-Jimmy

All comments

Jeyanthan I

Hey @Victor Rulev ,

If your intention is to identify and kill a hung build, how about configuring build monitoring that kills hung builds running in your remote agent?

Cheers, Jey