Push changelog from failed build into next successful build

[GoogleCodeExporter]

Currently Xinc will use the same build number for failed builds up until a
successful build. So, for example, if build 22 fails the first time, fails
the second time, and then passes you will have three Build.22 records in
your "All Builds" panel.

However, the change log for the incremental (failed) builds are attached to
the failed builds. I think they should propagate up to the successful
build. It's possible this is just my opinion, but considering one might
pull release information from a build, those changes would be "lost".

Original issue reported on code.google.com by [email protected] on 10 Jun 2008 at 6:05

[GoogleCodeExporter]

Original comment by [email protected] on 1 Oct 2011 at 11:14

• Added labels: Milestone-v3.0