It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,837

question asked: Jul 01 '11, 1:57 p.m.
question was seen: 3,685 times
last updated: Jul 01 '11, 1:57 p.m.

Related questions

JBE is sending a SIGKILL (9)

0
Amirsam Khataei (256●1●7●5) | asked Jul 01 '11, 1:57 p.m.
JAZZ DEVELOPER
Issue : JBE is sending a SIGKILL (9) upon build abandon. This is
keeping
any calling scripts, etc. from trapping the event and performing
followup
or cleanup steps. Please advise as to the ability to have JBE send
SIGTERM
instead. In addition, provide any documentation relevant to JBE
scripting,
APIs, etc.
This is limiting our ability to integrate RTC with an Enterprise-level
build solution.

3 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Brent Ulbricht (2.5k●1●1) | answered Jul 05 '11, 1:49 p.m.
JAZZ DEVELOPER
Issue : JBE is sending a SIGKILL (9) upon build abandon. This is
keeping
any calling scripts, etc. from trapping the event and performing
followup
or cleanup steps. Please advise as to the ability to have JBE send
SIGTERM
instead. In addition, provide any documentation relevant to JBE
scripting,
APIs, etc.
This is limiting our ability to integrate RTC with an Enterprise-level
build solution.


Hi,

What type of build definition template are you using for your build (ex. JBE - Command Line)?

Brent Ulbricht
RTC Build Lead
0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Jul 06 '11, 1:18 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The build team did implement a special build property for the ClearCase
Synchronizer (which uses the build machinery), to turn off that SIGKILL
behavior ... in particular, if we add the build property:
disableDestroyParticipant=true (see work item 164189).

Brent: Is there any reason why a customer should not use this flag?

Cheers,
Geoff


On 7/1/2011 2:08 PM, akhataei wrote:
Issue : JBE is sending a SIGKILL (9) upon build abandon. This is

keeping

any calling scripts, etc. from trapping the event and performing

followup

or cleanup steps. Please advise as to the ability to have JBE send

SIGTERM

instead. In addition, provide any documentation relevant to JBE

scripting,

APIs, etc.

This is limiting our ability to integrate RTC with an Enterprise-level

build solution.
0
permanent link
Brent Ulbricht (2.5k●1●1) | answered Jul 06 '11, 11:36 a.m.
JAZZ DEVELOPER
The build team did implement a special build property for the ClearCase
Synchronizer (which uses the build machinery), to turn off that SIGKILL
behavior ... in particular, if we add the build property:
disableDestroyParticipant=true (see work item 164189).

Brent: Is there any reason why a customer should not use this flag?

Cheers,
Geoff


On 7/1/2011 2:08 PM, akhataei wrote:
Issue : JBE is sending a SIGKILL (9) upon build abandon. This is

keeping

any calling scripts, etc. from trapping the event and performing

followup

or cleanup steps. Please advise as to the ability to have JBE send

SIGTERM

instead. In addition, provide any documentation relevant to JBE

scripting,

APIs, etc.

This is limiting our ability to integrate RTC with an Enterprise-level

build solution.


Hi,

That's what I was going to suggest if using the JBE command line build definition template.

Brent Ulbricht
RTC Build Lead

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.