It's all about the answers!

Ask a question

Which process keeps running on abandoning the build


man fire (7111210) | asked Apr 08 '10, 11:47 p.m.
Hi guys,

when u abandon a build, RTC warns that a server process will keep running. Now sometimes you do need to abandon builds so i'm wondering what process is that and how should we kill it so that it doesn't impact RTC's performance.

I currently kill the build engine that the build ran on and bring it back up again.Is that enough or should I be looking for something else?

Your help and views will be appreciated.Thanks!

2 answers



permanent link
David Olsen (5237) | answered Apr 09 '10, 7:00 p.m.
JAZZ DEVELOPER
manonfire wrote:
when u abandon a build, RTC warns that a server process will keep
running.

The message says that a process *may* continue to run, not that it will
continue to run.

Now sometimes you do need to abandon builds so i'm wondering
what process is that and how should we kill it so that it doesn't
impact RTC's performance.

When a build is abandoned, the build engine tries to kill the external
process that is doing the actual building. (On Linux I believe it sends
a SIGTERM signal to the process.) But the build engine cannot guarantee
that the process and all of its child processes will be killed. The
process may choose to ignore the signal. Or it may be killed but not
pass on the signal to any of its children. Or it might be hung so that
a SIGTERM has no effect.

To make sure nothing is left running after abandoning a build, you need
to log into the build machine, look for any processes that might be
associated with the abandoned build, and kill them. You may find that
for your builds abandoning the build does successfully kill all
processes and that you don't have to worry about this issue.

The point of the warning message when abandoning builds is that RTC
doesn't know whether or not processes are still running.

I currently kill the build engine that the build ran on and bring it
back up again.Is that enough or should I be looking for something
else?

I don't think that helps at all. I don't see how killing the build
engine will kill any other processes that were part of the abandoned
build. It's those processes that you need to worry about, not the build
engine process.

permanent link
Ralph Schoon (63.1k33645) | answered Apr 09 '10, 1:56 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi manonfire,

I believe the build runs in the context of the build engine. My interpretation of the warning in certain states is that the build might still perform some tasks that can't be interrupted. I have no long running build for testing, so I am not sure how long those could take.

I believe you should not have to kill the build engine process and restart it. In fact in most setups a user would not even know how to do that. Since you can run the build engine on several machines the impact on performance of RTC should be low if you don't run it on the RTC Server machine.

If you however kill the build engine and restart it, I would think all child processes should be terminated as well, provided the OS is advanced enough....

Ralph

Hi guys,

when u abandon a build, RTC warns that a server process will keep running. Now sometimes you do need to abandon builds so i'm wondering what process is that and how should we kill it so that it doesn't impact RTC's performance.

I currently kill the build engine that the build ran on and bring it back up again.Is that enough or should I be looking for something else?

Your help and views will be appreciated.Thanks!

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.