On 10 Jan 2013, at 11:06 AM, Gunnar Morling <gun...@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. --Hardy _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
