[Anthill-pro] Complex reporting system

[Uldis Karlovs-Karlovskis]

Hi Steve,
 
I`ve found an issue with this script. This is happening when one build is
waiting on lock. The target build have finished and when the event script is
analyzing last two builds, it takes a build which have been waiting on lock
so it is Running.
 
There is expanded log by me:
2007-10-22 11:52:31,339 WARN  71128 - First build status :
WorkflowStatusEnum[Running]
2007-10-22 11:52:31,340 WARN  71128 - Second build status :
WorkflowStatusEnum[Failed]
2007-10-22 11:52:31,340 WARN  71128 - Considered as different

 

 

Uldis Karlovs-Karlovskis, C. T. Co

 <mailto:uldis.karlovs-karlovskis at ctco.lv> uldis.karlovs-karlovskis at ctco.lv

 

-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Steve Boone
Sent: piektdiena, 2007. gada 12. oktobrī 20:51
To: AnthillPro user and support list.
Cc: AnthillPro user and support list.
Subject: Re: [Anthill-pro] Complex reporting system

 

Uldis,

Here is your script.  Let me know if you have any questions about it, or if
it gives you any problems.

Cheers,
Steve Boone
----

import com.urbancode.anthill3.domain.workflow.*;
import com.urbancode.anthill3.dashboard.* ;

boolean result = false;

if (event instanceof WorkflowEvent &&
        event.getCase().isComplete()) {
    Long wid = event.getCase().getWorkflow().getId();
    BuildLifeWorkflowCaseSummary[] blwcs=
DashboardFactory.getInstance().getBuildLifeWorkflowSummariesByWorkflow(wid,
null, new Integer(2));
    
    if(blwcs.length == 2){
        if(!blwcs[0].getStatus().equals(blwcs[1].getStatus())){
            result=true; 
            }
    }

}
    return result; 






On 10/12/07, Uldis Karlovs-Karlovskis < <mailto:uldisk at ctco.lv>
uldisk at ctco.lv > wrote:

That`s Great!

 

Uldis Karlovs-Karlovskis , C. T. Co

 <mailto:uldis.karlovs-karlovskis at ctco.lv> uldis.karlovs-karlovskis at ctco.lv

 

-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com [mailto:
<mailto:anthill-pro-bounces at lists.urbancode.com>
anthill-pro-bounces at lists.urbancode.com] On Behalf Of Steve Boone
Sent: piektdiena, 2007. gada 12. oktobrī 17:08
To: AnthillPro user and support list.
Cc: AnthillPro user and support list.
Subject: Re: [Anthill-pro] Complex reporting system

 

Uldis, 

I am working on getting this together for you now.

Regards,
Steve Boone

On 10/10/07, Uldis Karlovs-Karlovskis < uldisk at ctco.lv
<mailto:uldisk at ctco.lv> > wrote:

Hello!

I need to create specific system which filters build reports to send or not 
to send out to anthill users.

There must be algorithm when build is failed the mail sends out to clients.
All other builds after then must NOT be sent out until first successful
which is sent out. And again no build must be sent out until next failed 
build.
So it`s something like:
If(build_state != previos_build_state) trigger_event;

I know that this must be done in Event Selectors but I don`t know how! Can
You offer some script or solution?

Uldis Karlovs-Karlovskis, C. T. Co
uldis.karlovs-karlovskis at ctco.lv

_______________________________________________
Anthill-pro mailing list
Anthill-pro at lists.urbancode.com
http://lists.urbancode.com/mailman/listinfo/anthill-pro

 


_______________________________________________
Anthill-pro mailing list
Anthill-pro at lists.urbancode.com 
http://lists.urbancode.com/mailman/listinfo/anthill-pro

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20071022/763310b9/attachment-0003.htm