In regards to sending the email via CI instead of build script, I would tend to agree.
If someone checks out the code from source control and runs the build, should this recipient list be notified each time? How will you maintain the recipient list across different build environments to accommodate this? Do you actually want an email on success, or just failure? These all seem to be questions a CI solution like Jenkins already provides a way to answer. Jeremy D. Young Web Architect O'Reilly Auto Parts (417) 862-2674 x1858 Benjamin Muschko <[email protected]> wrote on 04/27/2011 11:24:14 AM: > From: Benjamin Muschko <[email protected]> > To: [email protected] > Date: 04/27/2011 11:31 AM > Subject: [gradle-user] Re: Sending an Email on Build Completion > > From my point of view the easiest way to achieve that would be to set up a > Continuous Integration server instead. It's easy to configure emails > individually for each project. Furthermore, it doesn't complicate your build > scripts. > > Ben > This communication and any attachments are confidential, protected by Communications Privacy Act 18 USCS ยง 2510, solely for the use of the intended recipient, and may contain legally privileged material. If you are not the intended recipient, please return or destroy it immediately. Thank you. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
