Ok, being a Hudson dude I'm quite worried I'm going to break the infrastructure though. But I'll give it a try.
/Anders On Tue, Aug 21, 2012 at 9:46 PM, Robert Scholte <[email protected]> wrote: > Sounds good, go ahead. > >> Date: Tue, 21 Aug 2012 21:45:18 +0200 >> From: [email protected] >> To: [email protected] >> Subject: Re: [mojo-dev] Why do we have two stages for CI plans? > >> >> Ok, I see. >> >> Today it looks like we build with Maven 2.2-something. Should we get >> Maven 3 build plans as well to ensure that it works? Maybe we could >> use Maven 3 for unit test and have IT plans for Maven 2.2.1 and latest >> Maven 3.x? >> >> /Anders >> >> On Tue, Aug 21, 2012 at 9:22 PM, Robert Scholte <[email protected]> >> wrote: >> > I'm responsible for that one. >> > >> > I've seen it quite often, that the unit tests succeed, but where >> > integration >> > tests fail. >> > Unit tests must always succeed, where as integration tests are preferred >> > to >> > all succeed. >> > In a case of an IT failure you can't always fix such issue fast/alone. >> > >> > This setup has to pro's: >> > - you can immediately see if it is a unit test or IT which causes the >> > job to >> > fail. >> > - you can (often shouldn't) disable the IT's. >> > >> > Robert >> >> Date: Tue, 21 Aug 2012 21:13:43 +0200 >> >> From: [email protected] >> >> To: [email protected] >> >> Subject: [mojo-dev] Why do we have two stages for CI plans? >> > >> >> >> >> Why do we have two stages for all/most CI plans? One for unit test and >> >> one for IT. As you all know IT will also do unit test (at least if we >> >> don't disable them which we don't). Makes no sense to me, but I guess >> >> there is some reason? >> >> >> >> /Anders >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe from this list, please visit: >> >> >> >> http://xircles.codehaus.org/manage_email >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
