I'm trying to integrate Hudson into our development process, and everything is going smooth except for one thing.
I had been using Phing to do deployments, and one of the things that was being triggered was an email to our tech support email address containing a list of all the commit messages between the last time code was deployed and the present SVN revision. I was doing something like this:
- read in a file from the root directory of the currently-deployed application that contains the SVN revision when the app was deployed
- place that value in a Phing variable
- insert that value into a command to send the SVN commit messages via email
- create a file in the root directory of the newly-deployed application that contains the current SVN revision
I'd like to be able to add that information to the email that gets sent out by Hudson when a successful build goes out. Any pointers on how to accomplish this task in Hudson would be greatly appreciated.
This annoyed me, too, when I switched from CruiseControl to Hudson. You can do what you need by using the Hudson email-ext plugin - after you install the plugin, you'll see an option "Editable email configuration" at the end of each job configuration page. Click on the help links to see what information you can include in your emails; the ${CHANGES} token is the one you need to shoe the SVN commits that triggered the build.
If the Hudson email-ext plugin is not enough have a look at the two following pages for a patch of the plugin. This patch allows the use of groovy scripts.
来源：https://stackoverflow.com/questions/2916105/sending-subversion-change-log-info-via-hudson