It's all about the answers!

Ask a question

Why is waitForTeamBuild for a child build waiting forever?

Yasuyuki Tominaga (297416) | asked Mar 10 '16, 2:26 a.m.
edited Mar 10 '16, 2:27 a.m.
There are 3 build definitions:
  "parent build"
  "child build 1" and
  "child build 2" ,
then I want to run the child builds within the parent build sequentially. I am using requestTeamBuild task to request "child build 1" then waitForTeamBuild to wait for "child build 1" completed as follows:

However, the build request "child build 1" will be in a JBE queue but it never proceed. It seems "parenet build" is waiting forever.  Why?


Accepted answer

permanent link
Taki Nakajo (1.1k2746) | answered Mar 10 '16, 2:39 a.m.
if you were running a single build engine, the both requests will go to the same build engine therefore the parent build is still running and the child build in the same build engine queue to wait so it never start because the parent build is waiting for the child build completed. It's deadlocked.
You need add one more build engine that supports these child builds. When you specify the new build engine in the child build definition, it will works as it is expected.

Note: if you run multiple Jazz Build Engine instances on the same machine, For more information, see Running multiple JBE processes.

Yasuyuki Tominaga selected this answer as the correct answer

Your answer

Register or to post your answer.