It's all about the answers!

Ask a question

Trigger Build Result Changed event


Michele Pegoraro (1.8k12110101) | asked Aug 07 '09, 5:27 a.m.
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?

5 answers



permanent link
Michele Pegoraro (1.8k12110101) | answered Aug 25 '09, 8:44 a.m.
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.

permanent link
Jared Burns (4.4k29) | answered Aug 07 '09, 8:28 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
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

permanent link
Michele Pegoraro (1.8k12110101) | answered Aug 24 '09, 5:58 a.m.
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?

permanent link
Michele Pegoraro (1.8k12110101) | answered Aug 24 '09, 9:43 a.m.
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...

permanent link
Michele Pegoraro (1.8k12110101) | answered Aug 25 '09, 8:18 a.m.
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?

Your answer


Register or to post your answer.