into multi-config jobs which run the MongoDB tests once embedded and once
against the external instance. The former has an additional configuration
axis for the JDK version (Java 6 and 7) as per Sanne's request. We can see
over the following days how this is going to work out.
--Gunnar
2013/7/10 Davide D'Alto <davide(a)hibernate.org>
+1
On Wed, Jul 10, 2013 at 11:15 AM, Sanne Grinovero <sanne(a)hibernate.org
>wrote:
> On 10 July 2013 10:12, Hardy Ferentschik <hardy(a)hibernate.org> wrote:
> >
> > On 10 Jan 2013, at 11:06 AM, Gunnar Morling <gunnar(a)hibernate.org>
> wrote:
> >
> >> I think the proper way of doing this kind of thing in Jenkins would be
> to
> >> set up a "multi-configuration" job which builds one project
applying
> >> different configurations (here once with embedded and once with
external
> >> MongoDB). This gives you separate as well as aggregated reports and
the
> >> overall build is marked as failed as soon as one of the configurations
> >> fails. You can see an example at [1].
> >
> > +1 I think that's the right approach. Builds which fail w/o apparent
> reason when
> > looking at the build report are a major pita and a sure recipe for
> people starting to
> > ignore these builds.
>
> +1
>
> >
> >
> > --Hardy
> _______________________________________________
> 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