|
Hello all, I have a question concerning the bissubscribe and/or the Event Toaster.
Current Solution: When a build is generated at 4h00am a perl script located in the <target>...</target> gets launched with the following instruction: <Exec Command="path_to_perl_script" IgnoreExitCode="true"/> This worked great until recently...anyhow...The problem with this approach is that, for each project we have, we create a new branch and with this branch we create 2 new Build Types: One Integration and the other Release. Now I need to manually add this instruction in the .target file. I would like to change that. In fact I would like to remove this instruction and move on with something more useful.
Here is my quest: I would like to create some sort of listener tool that would be installed on our teambuild machine. That listener would capture the "BuildCompletionEvent". It would filter the failed builds and call the perl script to automagically start the installation of that successful build.
I am faced with 2 possible scenario and I need your help figuring out which is the best approach.
Approach 1) Would be to have Visual Studio open (I believe) on the teambuild machine and use the Event Toaster PowerTool to invoke my perl script. This seems somewhat easy but I can't filter the failed builds and I have to leave the IDE open on the server. Unless I'm unaware of some option...
Approach 2) Would be to create some sort of listener that would capture the "BuildCompletionEvent", filter the quality of the build then take proper action such as start the install of that build (on another server for example)
The problem I have is that I don't seem to understand how do I capture the Event? In other words, what exactly is it sending? The Build Name? The Build Quality? I understand how to subscribe to an Event no problem but capturing it and doing stuff with it, is something I can't seem to understand.
Perhaps a small example would help or a link
Thanks in advace for any information Sincerely Vince |