That's fantastic James. And it puts the ball squarely in our court to get
it working.
Hope to get back to you soon.
-----Original Message-----
From: James Kovacs
Sent: Tuesday, December 07, 2010 4:42 PM
To: nhibernate-development
Subject: [nhibernate-development] Re: Failing Build Connection String
It is definitely possible to set up additional databases on
teamcity.codebetter.com. (I'm one of the admins for the CI servers. So
I know that it's possible.) :) @Richard - I'm not sure who was asked
before, but I don't remember it being discussed on the
[email protected] mailing list.
It's definitely a good idea to test the major dialects on the CI
server as it's a pain to get everything set up on your own developers
workstation. I'm as guilty as everyone for submitting patches after
only testing with SQL Server. I fully understand the overhead on a OSS
project of requiring all commit to be tested against a dozen DB
dialects. It wouldn't encourage contributions. We can eliminate some
of the risk by running the test suite against those dialects on the CI
server...
Anyway... We (the folks that run teamcity.codebetter.com) do not want
to encourage per-project dependency installation as it's too hard to
manage. Databases by their nature are often difficult/impossible to
bin deploy. Plus they are usable by multiple projects. So I have no
problem installing additional database servers on the CI server. I do
have one minor ask... Please install and get the setup running locally
with multiple databases. Once you've ironed out the details, feel free
to ping me and we can work together getting the appropriate databases
setup and configured on teamcity.codebetter.com. A link to the free
installer and installation instructions would be awfully helpful too.
Thanks,
James
On Dec 6, 10:15 am, Patrick Earl <[email protected]> wrote:
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
