Hi you surely can add it to the change request pool (JIRA) but why another notification type?
if it needs fixing : break the build if it does not need fixing : do not bother the programmer Am I missing something? In my setup, I have something similar, during the CI integration, some warnings may be ok. But when the button is pressed: 'ProjectXToQA', there may be NO warnings with kind regards Ruben Willems On Thu, Feb 5, 2009 at 1:25 PM, CinnamonDonkey < [email protected]> wrote: > > Hi All (Read as DevTeam ;), > > I have now set-up our incremental build process. The main purpose of > which is to run static code analysis on every change list submitted. > This analysis generates a build report which lists any code defects > detected and notifies the change list owner so that they can fix > their defects. > > The problem I have thougth is a build with defects is NOT a failed > build. The build is most likely successful. This means that currently > we must spam the user with emails for every build with and without > defects. > > Off course this means that sooner or later the end-users will start to > ignore their emails and will miss defects that need fixing. > > What would be handy is if we could define our own notification types. > This way I could create a notification type called "DEFECTS" and setup > the users to be emailed in the event of defects being detected in > their code. > > Is there currently a way of doing this? Is this something that could > be added to the change requests for post 1.4.3? > > Regards, > Shaun >
