Hi these options only exist in the nightly builds, or in the upcoming 1.4.4 release (very soon)
with kind regards Ruben Willems On Mon, Apr 13, 2009 at 7:53 PM, adickinson <[email protected]> wrote: > > I'm using version 1.4.3 and the > 'stopProjectOnReachingMaxSourceControlRetries' and > 'sourceControlErrorHandling' items do not exist. Am I missing an > update? > > On Apr 6, 12:59 pm, Ruben Willems <[email protected]> wrote: > > Hi > > > > take a look at the project configuration block: > > the latest builds have some updates that would improve a lot. > > > > http://confluence.public.thoughtworks.org/display/CCNET/Project+Confi... > > > > options : > > maxSourceControlRetries > > stopProjectOnReachingMaxSourceControlRetries > > sourceControlErrorHandling > > > > Let me know if these helped or not. > > > > with kind regards > > Ruben Willems > > > > On Thu, Mar 19, 2009 at 5:42 PM, Jon W <[email protected]> wrote: > > > > > Hi Ruben, > > > > > ccnet-1423 would be helpful to avoid sending developers the exceptions. > > > > > notification=change would become notification=fixed,failed > > > > > I would still like to avoid the build state becoming failed due to an > > > exception. If the state change is not caused by a source code commit, > > > then it should be logged only to the administrator of the build system > > > and not alert the developers through cctray, emails, etc... > > > > > Thanks, > > > Jon > > > > > On Thu, Mar 19, 2009 at 9:24 AM, Ruben Willems < > [email protected]> > > > wrote: > > > > Hi > > > > > > I had already made a similar issue > > > >http://jira.public.thoughtworks.org/browse/CCNET-1423 > > > > > > Would this also be a solution for you ? > > > > > > with kind regards > > > > Ruben Willems > > > > > > On Thu, Mar 19, 2009 at 4:23 PM, Jon W <[email protected]> wrote: > > > > > >> Yes, I know about the filter trigger, but the network administration > > > >> times can be random. I also don't want to shut down or reconfigure > 5 > > > >> ccnet servers every time I need to take the svn server offline. I'd > > > >> rather just not see the build exceptions or see the build state > change > > > >> due to regular maintenance. I'm okay with exception emails being > sent > > > >> to the ccnet admin, but the build state should be left alone as > there > > > >> weren't any source code modifications to cause the failed build. > > > > > >> Thanks, > > > >> Jon > > > > > >> On Thu, Mar 19, 2009 at 9:18 AM, Ruben Willems < > [email protected] > > > > > >> wrote: > > > >> > Hi > > > > > >> > if the IT departement does this at fixed times, let say always > between > > > >> > 22:00 > > > >> > and 23:00 > > > >> > you can use the filter trigger : > > > > >http://confluence.public.thoughtworks.org/display/CCNET/Filter+Trigger > > > > > >> > with kind regards > > > >> > Ruben Willems > > > > > >> > On Thu, Mar 19, 2009 at 4:13 PM, Jon W <[email protected]> wrote: > > > > > >> >> I've created jira issue 1425: > > > >> >> http://jira.public.thoughtworks.org/browse/CCNET-1425 > > > > > >> >> I've been seeing exceptions when ccnet pings the svn server and > is > > > >> >> unsuccessful when checking for modifications. If the IT > department > > > is > > > >> >> occasionally taking the network offline for a couple of minutes, > then > > > >> >> I don't need to see that ccnet was unable to connect to the svn > > > >> >> server. This usually happens in the middle of the night, and the > > > >> >> extra build failures sent to the developers causes them to start > > > >> >> ignoring build failures as just another system fluke. > > > > > >> >> Personally, I don't think that the build state should be "failed" > > > just > > > >> >> for the ccnet server being temporarily unable to communicate with > the > > > >> >> svn server. This should be logged in ccnet.log as before, and/or > an > > > >> >> email can be sent to the ccnet admin. Changing the build state > due > > > to > > > >> >> the network being offline temporarily will only cause people to > > > ignore > > > >> >> the real broken builds. > > > > > >> >> Any chance that exceptions can just be logged and stay out of the > > > >> >> build status as was the case pre-1.4.3? > > > > > >> >> Thanks, > > > >> >> Jon > > > > > >> >> On Thu, Mar 19, 2009 at 1:20 AM, Ruben Willems > > > >> >> <[email protected]> > > > >> >> wrote: > > > >> >> > Hi > > > > > >> >> > indeed there was the PublishExceptions option, but that was > > > removed, > > > >> >> > and the reason why is very obscure. > > > > > >> >> > Please file a jira request, and we'll see when we can add it > in. > > > >> >> > But what would the desired result be? > > > >> >> > PublishExceptions is set to false > > > >> >> > exception occured : > > > >> >> > --> do not run the publisher block (this sounds easy) > > > > > >> >> > Is this ok? > > > >> >> > the state of the build will still be 'Exception' > > > > > >> >> > with kind regard > > > >> >> > Ruben Willems > > > > > >> >> > On Wed, Mar 18, 2009 at 4:30 PM, Jon W <[email protected]> > wrote: > > > > > >> >> >> There used to be a PublishExceptions option in the project > block > > > >> >> >> that > > > >> >> >> would allow the user to disregard all exceptions (removed in > ccnet > > > >> >> >> 1.1). Is there anything similar that can be used? I haven't > ever > > > >> >> >> needed email notification regarding exceptions, as if there is > a > > > >> >> >> rare > > > >> >> >> issue, then I just review the ccnet.log. > > > > > >> >> >> I went back to 1.4.2, but would hope to have a workaround in > 1.4.4 > > > >> >> >> if > > > >> >> >> possible. Please let me know if you want me to file an issue > or > > > >> >> >> request. > > > > > >> >> >> Thank you, > > > >> >> >> Jon > > > > > >> >> >> On Tue, Mar 17, 2009 at 12:35 PM, Ruben Willems > > > >> >> >> <[email protected]> > > > >> >> >> wrote: > > > >> >> >> > Hi > > > > > >> >> >> > it is part of 1.4.3 > > > > > >> >> >> > 1.4.2 does not know this state > > > > > >> >> >> > with kind regards > > > >> >> >> > Ruben Willems > > > > > >> >> >> > On Tue, Mar 17, 2009 at 5:53 PM, Jon W <[email protected]> > > > wrote: > > > > > >> >> >> >> fyi, CCNet service will not start unless the user names are > > > >> >> >> >> unique. > > > >> >> >> >> I'm not sure if this will have other issues with > notifications > > > by > > > >> >> >> >> having multiple user names for the same person. > > > > > >> >> >> >> <users> > > > >> >> >> >> <user name="ben" group="developersfailed" > > > >> >> >> >> address="[email protected]"/> > > > >> >> >> >> <user name="ben222" group="developersfixed" > > > >> >> >> >> address="[email protected]"/> > > > >> >> >> >> </users> > > > > > >> >> >> >> Do you know when the "exception" became part of the > "change" > > > >> >> >> >> email > > > >> >> >> >> notification? I would like to use 1.4.2 if that doesn't > have > > > >> >> >> >> this > > > >> >> >> >> behavior. > > > > > >> >> >> >> Thank you, > > > >> >> >> >> Jon > > > > > >> >> >> >> On Tue, Mar 17, 2009 at 1:20 AM, Ruben Willems > > > >> >> >> >> <[email protected]> > > > >> >> >> >> wrote: > > > >> >> >> >> > Hi > > > > > >> >> >> >> > good point, maybe we should foresee a way so you can add > > > >> >> >> >> > multiple > > > >> >> >> >> > notifications in the groups element. > > > > > >> >> >> >> > For the moment you can have the same effect, but you will > > > need > > > >> >> >> >> > to > > > >> >> >> >> > place > > > >> >> >> >> > the > > > >> >> >> >> > user in 2 groups :-( > > > > > >> >> >> >> > <users> > > > >> >> >> >> > <user name="ben" group="developersfailed" > > > >> >> >> >> > address="[email protected]"/> > > > >> >> >> >> > <user name="ben" group="developersfixed" > > > >> >> >> >> > address="[email protected]"/> > > > >> >> >> >> > .. > > > >> >> >> >> > </users> > > > > > >> >> >> >> > <groups> > > > >> >> >> >> > ... > > > >> >> >> >> > <group name="developersfixed" > > > notification="fixed"/> > > > >> >> >> >> > <group name="developersfailed" > > > >> >> >> >> > notification="failed"/> > > > >> >> >> >> > </groups> > > > > > >> >> >> >> > this will have the same effect > > > > > >> >> >> >> > Lets see what the otter devs think on this > > > > > >> >> >> >> > with kind regards > > > >> >> >> >> > Ruben Willems > > > > > >> >> >> >> > On Mon, Mar 16, 2009 at 9:37 PM, Jon W < > [email protected]> > > > >> >> >> >> > wrote: > > > > > >> >> >> >> >> Hi. I just upgraded to 1.4.3. When ccnet experienced > > > network > > > >> >> >> >> >> issues > > > >> >> >> >> >> talking to the svn server, everybody was sent a couple > of > > > >> >> >> >> >> Exception > > > >> >> >> >> >> emails. How can I configure ccnet, so regular > developers > > > >> >> >> >> >> don't > > > >> >> >> >> >> have > > > >> >> >> >> >> to see the network hiccups? The exceptions are more for > the > > > >> >> >> >> >> sysadmin > > > >> >> >> >> >> people, and not developers who only need to see if the > > > source > > > >> >> >> >> >> code > > > >> >> >> >> >> builds correctly. Is the Exception supposed to be in > the > > > >> >> >> >> >> "change" > > > >> >> >> >> >> notification group? > > > > > >> >> >> >> >> Currently the configuration is: > > > > > >> >> >> >> >> <email from="[email protected]" mailhost="smtp.me.com" > > > >> >> >> >> >> includeDetails="TRUE"> > > > >> >> >> >> >> <users> > > > >> >> >> >> >> <user name="jon" group="buildmaster" > > > >> >> >> >> >> address="[email protected]"/> > > > >> >> >> >> >> <user name="howie" group="buildmaster" > > > >> >> >> >> >> address="[email protected]"/> > > > >> >> >> >> >> <user name="val" group="buildmaster" > > > >> >> >> >> >> address="[email protected]"/> > > > > > >> >> >> >> >> <user name="ben" group="developers" > > > >> >> >> >> >> address="[email protected]"/> > > > >> >> >> >> >> <user name="bob" group="developers" > > > >> >> >> >> >> address="[email protected]"/> > > > >> >> >> >> >> <user name="bill" group="developers" > > > >> >> >> >> >> address="[email protected]"/> > > > >> >> >> >> >> </users> > > > >> >> >> >> >> <groups> > > > >> >> >> >> >> <group name="developers" > notification="change"/> > > > >> >> >> >> >> <group name="buildmaster" > > > notification="always"/> > > > >> >> >> >> >> </groups> > > > > > >> >> >> >> >> <converters> > > > >> >> >> >> >> <regexConverter find="$" replace="@me.com" > /> > > > >> >> >> >> >> </converters> > > > >> >> >> >> >> </email> > > > > > >> >> >> >> >> Thank you, > > > >> >> >> >> >> Jon >
