[Anthill-pro] Notification scheme best practices

[Yanko, Curtis]

We have a notify on failure and first success too but truthfully I think
everyone should get every email. The point of our build service is to
increase quality and collaboration by making the process transparent. CI
reduces feedback loop times. Even if all is going we'll I want team
members to see who is doing what. If they want to ignore it all....
That's what inbox rules are for!

For our own part I filter every build notification into three folders,
Success, Failure and Error so I can keep my finger on the pulse and nip
problems in the bud.

===
-Curt
W: 860.702.9059
M: 860.881.2050

-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of emerson
cargnin
Sent: Thursday, May 29, 2008 12:11 PM
To: AnthillPro user and support list.
Subject: [Anthill-pro] Notification scheme best practices

Hi Guys

I'm sending this to try to collect some best practices to use with
anthill. I honestly think the default schemas are not sufficient.

* Building notifications:

- CI and build from a tag- Each CI workflow (or one if you don't have ci
for branches) uses a CI notifications scheme. I configured it to send to
all users, and I added a case selector called "change status selector"
that checks if status changed for that workflow. So if it has success
always it won't send an email, only when it fails, and then will only
send again when it is fixed. This is the configuration that I used to
use in cruisecontrol. Good idea to have it
out-of-the-box:

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;

- Pure Trunk builds: I use a sendOnAFailure notification schema, which
uses the workflow fails workflow selector.


* Deployment Notifications:

-  use a sendOnAFailure notification schema, which uses the workflow
fails workflow selector.

I think in adding other user selectors as well, as creating a role for
who wants to be notified of any deployment or build, or sending message
always to the committer.


It would be great to know what approach other people are using when
setting notifications.

By the way, the UserLookup.getAllContributers(workflow); return all
users that committed since the last build???

Templates:

I think the email template (changelog) that comes with anthill is a bit
messy and doens't show relevant information. I changed it slightly to
show the project and skip empty jobs. Have some one created some
interesting templates? Like for example not showing all steps with
success, or having only a summary of the build with any failed steps...

thanks
emerson


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


This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to 
which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the 
sender by replying to this message and delete this e-mail immediately.