Notifications not working in Go 2.1

Follow

Comments

4 comments

  • Avatar
    Anandha Krishnan

    Mike,


    We tested this scenario on upgrade and the emails notifications seem to be working fine. Could you provide us with more details (logs, platform etc) or alternatively file a support ticket.


    Thanks,


    Go Dev Team

  • Avatar
    Mike O'Brien

    Anand,


    I'll look into it further on my end and get back to you. I just wanted to see if this was a known issue before I spent too much time on it.


    We are running the latest release of Go on Windows Server 2008 R2 (Which only comes in the x64 flavour). 


    Thanks,


    m

  • Avatar
    Rajeshvaran Appasamy

    Hi Mike,


    There is no known issue currently in the above context. We had also tried it with Windows Server 2008 R2. This is for your confirmation.

  • Avatar
    Mike O'Brien

    Ok, I think I figured out what is causing this. We originally stored our Go config file (C:\Program Files (x86)\Go Server\config\cruise-config.xml) on the D drive of our server (D:\Release\Config\cruise-config.xml). We updated the path in the wrapper config to specify the new location (C:\Program Files (x86)\Go Server\config\wrapper-server.conf):


    wrapper.java.additional.8="-Dcruise.config.file=D:\Release\Config\cruise-config.xml"


    Until we upgraded to version 2.1 everything worked fine. After we upgraded to 2.1 we could not get build notifications to work even though a test email could be sent out successfully. What we found was that if we put our cruise-config.xml back under the config folder (C:\Program Files (x86)\Go Server\config\) the notifications would work. Move it back out to the D drive and no workie. I have no idea why the location of the config file would just effect the build notifications (You would think it would break other things as well). We could not come up with an answer. 


    In any event, we're storing the config file under the Go config folder and that is working for us. But I wanted to pass this along if you wanted to check this out. Maybe there is a bug and this scenario is bringing it to the fore.

Please sign in to leave a comment.