I’ve asked this before, and my understanding is we’re not gonna be able to get anything other than SQL-Server on the TeamCity server.
However, +1 for the idea. So if we can come up with some servers, we should get builds running for as many dialects as we can. I’d also like to see them reporting a fail whenever a given test for a dialect that was previously passing is now broken. (A little more work, but I’m sure we could do it.) From: Patrick Earl Sent: Monday, December 06, 2010 5:15 PM To: [email protected] Subject: Re: [nhibernate-development] Failing Build Connection String Good to know Fabio. Thanks! BTW, does anyone know about the possibility of setting up databases other than MSSQL on teamcity.codebetter.com? Would be nice if there were separate build configurations for different databases so that even if all tests aren't supported, it would be easy to see what's happening across the board. There are a million databases and versions out there, so it would be hard to cover everything, but even having recent versions of a few major ones would be helpful. Patrick Earl On Mon, Dec 6, 2010 at 9:39 AM, Fabio Maulo <[email protected]> wrote: Each developer "should" have his hibernate.cfg.xml in the nhibernate\src\NHibernate.Test (and other tests). Before run tests the file is copied in the binaries folder and our TestCase will override the configuration defined in App.config with the configuration of hibernate.cfg.xml. Here is where is the magic private void Configure() { cfg = new Configuration(); if (TestConfigurationHelper.hibernateConfigFile != null) cfg.Configure(TestConfigurationHelper.hibernateConfigFile); I have 3 conf: FireBird.hibernate.cfg.xml MSSQL.hibernate.cfg.xml Oracle.hibernate.cfg.xml My override configuration for SQL server is: <hibernate-configuration xmlns="urn:nhibernate-configuration-2.2" > <session-factory name="NHibernate.Test"> <property name="connection.driver_class">NHibernate.Driver.SqlClientDriver</property> <property name="connection.connection_string"> Data Source=localhost\SQLEXPRESS;Initial Catalog=NHTEST;Integrated Security=True;Pooling=False </property> <property name="adonet.batch_size">10</property> <property name="show_sql">false</property> <property name="dialect">NHibernate.Dialect.MsSql2008Dialect</property> <property name="use_outer_join">true</property> <property name="command_timeout">10</property> <property name="query.substitutions">true 1, false 0, yes 'Y', no 'N'</property> <!--<property name="query.factory_class"> NHibernate.Hql.Classic.ClassicQueryTranslatorFactory, NHibernate </property>--> </session-factory> </hibernate-configuration> The adonet.batch_size is important because I would avoid some surprise (as as happened in the past). On Mon, Dec 6, 2010 at 1:31 PM, Fabio Maulo <[email protected]> wrote: Personally I never used 'TestDatabaseSetup'. On Mon, Dec 6, 2010 at 1:21 PM, Patrick Earl <[email protected]> wrote: Looks like back in March, the connection string was hard-coded into NHibernate.TestDatabaseSetup/TestDatabaseSetup.cs to make the test database setup pass on the build server. That causes problems with running the tests from the NAnt scripts locally though, so I removed it realizing the build might fail. Indeed, the build has failed. Does anyone happen to have any thoughts on what the root cause of the problem might be? Patrick Earl -- Fabio Maulo -- Fabio Maulo
