[JIRA] Commented: (CC-975) Local working copy with incorrect svn repository address causes exception and sends a bunch of emails

    [ http://jira.public.thoughtworks.org/browse/CC-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_18967 ] 

Dan Rollo commented on CC-975:
------------------------------

JIRA is not a tool for general support, only for managing patches and known bugs. 

The first line of support in all cases is actually the user mailing list: 

https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user 

I recommend you post your issues to the user mailing list. 


> Local working copy with incorrect svn repository address causes exception and sends a bunch of emails
> -----------------------------------------------------------------------------------------------------
>
>                 Key: CC-975
>                 URL: http://jira.public.thoughtworks.org/browse/CC-975
>             Project: CruiseControl
>          Issue Type: Bug
>          Components: Core Application
>    Affects Versions: 2.8
>         Environment: Fedora 11 server
>            Reporter: Lisa Tanguay
>
> This happened after we physically moved out  server from domain name abc.com to def.com. We copied the entire CRUISECONTROL_FOLDER folder from one server to the other and updated config.xml to remove all references to the old server. The subversion repository, containing all our projects, was also moved to the new server and was working fine by itself. We set config.xml to reference the new subversion repository addresses, so all seemed fine, except that no projects would build. After the server move, we added another project to CruiseControl that build fine and but would force the other projects to build if changes were sensed. 
> At this point in time we had one project that would build fine in CruiseControl and several projects that wouldn't build at all.
> Moving on, a user on our team commits bad code and CruiseControl starts throwing "project failed" messages, as expected.
> In config.xml, we've set fail emails to send everyday between 6am and 8pm, once every hour, which CruiseControl did, except at 7PM every single day the project was broken it would randomly send around 90 to 250 emails, about 30 seconds apart. At 8PM it would stop sending emails, and would resume the next day at it's scheduled time, but would start acting strangely at 7PM again. So instead of getting the normal 14 CruiseControl fail emails a day (one for every hour), we were getting something like ~150 emails. 
> After some investigations in the logs, I discovered the following exception in the logs:
> 2010-02-02 10:52:52,065 [Thread-76] INFO  Project          - Project my_project:  idle
> 2010-02-02 10:52:52,069 [Thread-76] INFO  ProjectController - my_projectController: build progress event: idle
> 2010-02-02 10:52:52,069 [Thread-76] ERROR Project          - exception attempting build in project my_project
> net.sourceforge.cruisecontrol.CruiseControlException: svn process exited with error code 1
>         at net.sourceforge.cruisecontrol.util.CommandExecutor.executeAndWait(CommandExecutor.java:119)
>         at net.sourceforge.cruisecontrol.util.Commandline.executeAndWait(Commandline.java:635)
>         at net.sourceforge.cruisecontrol.bootstrappers.SVNBootstrapper.bootstrap(SVNBootstrapper.java:134)
>         at net.sourceforge.cruisecontrol.Project.bootstrap(Project.java:760)
>         at net.sourceforge.cruisecontrol.Project.build(Project.java:192)
>         at net.sourceforge.cruisecontrol.Project.execute(Project.java:147)
>         at net.sourceforge.cruisecontrol.ProjectConfig.execute(ProjectConfig.java:404)
>         at net.sourceforge.cruisecontrol.ProjectWrapper.run(ProjectWrapper.java:69)
> We were getting one of these exceptions for every project that previously was not building in CruiseControl. Every time this exception was generated, another email would be sent, but then CruiseControl would try to build the same project again 30 seconds later and get the same exception and send the same email.
> After even further investigation, and setting CruiseControl to debug, I discovered that my local working copies of each project still referenced the svn repository on the old server, which did not exist anymore. Config.xml was correct and pointed to the new server, but the invisible .svn folders located in each of my local working copy folders still pointed to the old server. So I rechecked out all my projects using the new repository address and CruiseControl resumed working normally.
> So this issue was solved, but CruiseControl shouldn't be sending  hundreds of emails a day if an exception is thrown. Due to a recent code reform, we broke a lot of our javadoc code and haven't got around to fixing them, so the compiler created a lot of JavaDoc warnings, which generated over 500Kb CruiseControl emails. 
> So over 100 emails at 500Kb were being sent to each person on our team a day. Needless to say,  a lot of inboxes were filled. :P

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d