Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Trigger Build Result Changed event

Hi, I have create an event handler to Build Result Changed event and I was trying to debug it, but it has started only one time, on the first time I've launched the build. All sequent build doesn't trigger the event and so the handler doesn't run too.

How this event is triggered? And when?

0 votes



5 answers

Permanent link
I've use the event title to retrieve the different event:


Started: BuildDefinitionName
Started Activity: BuildDefinitionName BuildLabel (pre-build settings)
Started Activity: BuildDefinitionName BuildLabel (change-set acceptation)
Started Activity: BuildDefinitionName BuildLabel (file retrieving)
Activity Completed: BuildDefinitionName BuildLabel (pre-build settings)

Succeded: BuildDefinitionName BuildLabel
Failed: BuildDefinitionName BuildLabel


I hope it could be usefull for someone else.

1 vote


Permanent link
On Fri, 07 Aug 2009 09:38:04 +0000, mikyjpeg wrote:

Hi, I have create an event handler to Build Result Changed event and I
was trying to debug it, but it has started only one time, on the first
time I've launched the build. All sequent build doesn't trigger the
event and so the handler doesn't run too.

How this event is triggered? And when?

Not sure what causes the Build component to generate their events, but it
might be helpful to know that the Process component handles the events
asynchronously. Our asynchronous processing of events runs every 25
seconds by default, so if you're debugging your breakpoint might not get
hit right away.

--
Jared Burns
Jazz Process Team

0 votes


Permanent link
On Fri, 07 Aug 2009 09:38:04 +0000, mikyjpeg wrote:

Not sure what causes the Build component to generate their events, but it
might be helpful to know that the Process component handles the events
asynchronously. Our asynchronous processing of events runs every 25
seconds by default, so if you're debugging your breakpoint might not get
hit right away.



I've try to wait but it doesn't seems to run. I've also tried out of debug, creating a file to watch if it has run, and it has run only after the first build. All the other build does not trigger the handler.

Any idea on how to debug this problem?

0 votes


Permanent link
I suppose that the little frames that appear on right bottom of client contaning build results are triggered using a similar event handler. But they appear as my handler is not called...

0 votes


Permanent link
Honestly I don't know why and what I've done, but now it seems to be called. Also, it does run too much: I request a single build and it is triggered six times. First time state is "In progress" but from the second one state is "COMPLETED" and status is always "KO" (i'm testing a dummy build that always fails).
Why is it called all these times? Does someone knows exactly when Build Result changes?

0 votes

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 10,936

Question asked: Aug 07 '09, 5:27 a.m.

Question was seen: 6,974 times

Last updated: Aug 07 '09, 5:27 a.m.

Confirmation Cancel Confirm