Generating a change log from build publishers

"Ron Rader" <[email protected]>
Newsgroups gmane.comp.java.cruise-control.user
Message-ID <6BA04340F278EB47AB42AAF2EED9CBBA033D4C2D@dellserver.cipheroptics.local>
  I haven't seen this issue covered in quite a bit of Googling and
reading the CruiseControl configuration reference, so I'm hoping someone
out there might have a tip.

  We have a working automated build and test system run on
CruiseControl.  I need to generate a single change log for reference.
This log needs to include the build label, date, and modification list
at minimum.

  The XML Log File and the digested HTML page available underneath the
CruiseControl HTTP status page contain the required information in the
<modifications> and <info> sections.  We need a change log in order to
prevent having to click around multiple pages to correlate a change to a
particular build.

  Is there a way using the existing publishers supplied with
CruiseControl to append the <modifications> and <info> build information
to a single source?  I don't want just a buildresultsurl.  I've tried
fooling around with the email/htmlemail publishers but haven't gotten
very far.

  If anybody has any tips on adding <modifications>/<info> to either a
mail publisher or the weblog publisher, I'd love to read them.

  Thanks in advance!

  Regards,

  Ron Rader



The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting all copies. Thank you.

------------------------------------------------------------------------------
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.