Josh Knowles
2007-Jun-15 21:19 UTC
[Cruisecontrolrb-users] Best Practices for Testing Multiple Databases
On most projects I work on the development database (sqlite3) is usually different then production (mysql5). As I want to make sure I run my specs against both environments I have set up two cc projects, and configuring the two databases accordingly. This works fine but is a bit annoying as I receive duplicate emails/notifications when something non-database related breaks. Has anyone come up with a better solution for managing multiple databases? Ideally I''d like this support built right in, so that if a spec broke on both databases I only received a single notification. If this is of enough interest to others I can look at patching. Josh -- Josh Knowles joshknowles at gmail.com http://joshknowles.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070615/66eebea2/attachment.html
Rolf Russell
2007-Jun-15 23:11 UTC
[Cruisecontrolrb-users] Best Practices for Testing Multiple Databases
If you checkout the head of CC.rb (release 1.2 in progress) you can trigger one build off of another. I believe the syntax is " project.triggered_by :other_project". So if your mysql5 build is triggered by the sqlite3 build, and the sqlite3 build breaks, then the mysql5 build won''t even run. Alternately you could combine both builds into one big build that runs them sequentially. --Rolf "Josh Knowles" <joshknowles at gmail.com> Sent by: cruisecontrolrb-users-bounces at rubyforge.org 06/15/2007 04:19 PM To cruisecontrolrb-users at rubyforge.org cc Subject [Cruisecontrolrb-users] Best Practices for Testing Multiple Databases On most projects I work on the development database (sqlite3) is usually different then production (mysql5). As I want to make sure I run my specs against both environments I have set up two cc projects, and configuring the two databases accordingly. This works fine but is a bit annoying as I receive duplicate emails/notifications when something non-database related breaks. Has anyone come up with a better solution for managing multiple databases? Ideally I''d like this support built right in, so that if a spec broke on both databases I only received a single notification. If this is of enough interest to others I can look at patching. Josh -- Josh Knowles joshknowles at gmail.com http://joshknowles.com _______________________________________________ Cruisecontrolrb-users mailing list Cruisecontrolrb-users at rubyforge.org http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070615/6e8b3880/attachment.html