6:58 a.m.
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
7:03 a.m.
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
7:32 a.m.
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
8:04 a.m.
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
8:11 a.m.
Sounds like a good idea to have CI verify both embedded and "installed".
But that's next, I'd first want to see it building at least with the
installed MongoDB.
On 4 July 2013 14:04, Davide D'Alto <davide(a)hibernate.org> wrote:
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
8:18 a.m.
Sto guardando
On Thu, Jul 4, 2013 at 2:11 PM, Sanne Grinovero <sanne(a)hibernate.org> wrote:
Sounds like a good idea to have CI verify both embedded and
"installed".
But that's next, I'd first want to see it building at least with the
installed MongoDB.
On 4 July 2013 14:04, Davide D'Alto <davide(a)hibernate.org> wrote:
> 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
>
>
8:58 a.m.
Should be fixed now, the last build is building the MongoDB modules.
The environment variable is missing in the build.
Now that I think about it...didn't we created a separate job for mongodb in
the past? I think the Idea was two build the project without using the
remote container and then
build using th remote container if everything is fine.
I don't see the build using mongodb though and right now I've just added
the MONGODB_HOSTNAME in the configuration of the master build and pull
request build
On Thu, Jul 4, 2013 at 2:18 PM, Davide D'Alto <davide(a)hibernate.org> wrote:
Sto guardando
On Thu, Jul 4, 2013 at 2:11 PM, Sanne Grinovero <sanne(a)hibernate.org>wrote:
> Sounds like a good idea to have CI verify both embedded and "installed".
>
> But that's next, I'd first want to see it building at least with the
> installed MongoDB.
>
> On 4 July 2013 14:04, Davide D'Alto <davide(a)hibernate.org> wrote:
> > 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
> >
> >
>
4160
days inactive
4160
days old
6 comments
4 participants
participants (4)
-
Davide D'Alto -
Emmanuel Bernard -
Gunnar Morling -
Sanne Grinovero