Community
Participate
Working Groups
For some components that tend to build up large numbers of unreleased changes (e.g. j2ee), committers often are not able to immediately release their own changes and a whole queue of changes added by multiple individuals is later released by a single person. This perhaps speaks to a need for a project-specific process change (i.e. don't let large numbers of unreleased changes queue up) but it would be great if the build notification logic could send emails to the union of the CVS accounts that committed the relevant changes and the accounts that released the changes.
Ok, so you are saying only the person who does the release get's the email? I can investigate, but sounds like we'd have to write some custom code to do this ... that is, it's not "built in" to CC. But, I'll take a look, but will likely take a while. Thanks,
I'm not sure how to do this with CVS or cruisecontrol (and, not really sure what the current undesired behavior it) but will consider well integrated and well tested patches.
I haven't taken a look or worked with Cruise Control that much, but an alternative build system, called Luntbuild provides this ability by default. Might be something look at for the future. http://luntbuild.javaforge.com/ It's Apache 2.0 licensed.
Is there an easy place to hook into the end of a build? (eg., shell or ant script?) If so, you could look at using a Search CVS database query to pull up the list of committer(s) relevant to that build. Steps to implement would be: a) at start of build, run a database update to ensure contents are current (using shell or ant to call a web API) b) at end of build, query the database for changes by branch the relevant date range; collect cvs usernames, and do something with those to turn them into email addresses (perhaps as simple as `finger $username` on the build server?) If you're interested in this approach, let me know and I can provide more details.
I am blindly closing old bugs as "won't fix" (I selected those opened over two years ago, mostly opened by me, with no comments made in past couple of years). This is entirely an effort to focus on relevant bugs ... so if anyone sees any of these old bugs closed as "won't fix" that _are_ still relevant, do feel free to reopen. It would be much appreciated to know it was still important and deserves some attention beyond a blind close. Apologies in advance for closing any prematurely.
