Re: [hibernate-dev] [OGM] CI and MongoDB tests
Why not to test the emebedded one on a port that is different from the
default one (or the one used for the remote mongodb)?
This way if you are using the emebedded the remote is not affected.
On Thu, Jul 4, 2013 at 1:32 PM, Sanne Grinovero <sanne(a)hibernate.org> wrote:
Actually makes me think we might want an option in OGM-295 to have
the
build fail if MongoDB is only runnable in embedded mode:
MongoDB is installed in the CI machine and used to be run
successfully. I guess the configuration changed and we didn't notice
it stopped building it.. that must be it because the build numbering
was also reset and I'm not finding build logs from the older runs.
Davide is that something you could look at? Today I really need to
push back on any new task :-(
On 4 July 2013 13:03, Gunnar Morling <gunnar(a)hibernate.org> wrote:
> It's my hope that one of the benefits of implementing OGM-295
("Facilitate
> project setup by using Embedded MongoDB", [1]) is to enable this.
>
> We still could consider running tests against a standalone installation
of
> MongoDB, but starting with testing against an embedded instance seems
like
> a good first step to me.
>
> --Gunnar
>
> [1] https://hibernate.atlassian.net/browse/OGM-295
>
>
>
> 2013/7/4 Emmanuel Bernard <emmanuel(a)hibernate.org>
>
>> >From what I can see and understand the OGM builds (hibernate-ogm-master
>> specifically) do not test MongoDB. Is that something expected? Can we
>> envision adding MongoDB testing?
>>
>> Emmanuel
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev