Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Can I accidentally kill processes from another build?

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?

2 answers

1 accepted

0 votes
Answer accepted
Jimmy Seddon
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 19, 2020

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!


1 vote
Jeyanthan I
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 19, 2020

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

I don't have access to that and I need a more "localized" solution. Besides, hung tests could be detected within 10 minutes, while timeout for a hung build could be a few hours.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events