Well we already have that in a sense - all the tests still run and we can see which fail even if findbugs/pmd/checkstyle have lots of complaints.
My concern would be having 2 separate Jenkins tasks would make it even easier to ignore the non-test warnings. I'd much rather make "mvn test" fail when findbugs/pmd/checkstyle counts go up, or drop those tasks from Jenkins entirely. This would let us all test against the same rules as Jenkins in a straightforward way. I'm only bringing this up because it bugs me that I'm starting to mentally bit-bucket "build is unstable" email, which is a terrible habit. -tom On Wed, Mar 7, 2012 at 3:59 PM, Dmitriy Lyubimov <dlie...@gmail.com> wrote: > On Tue, Mar 6, 2012 at 10:04 PM, Paritosh Ranjan <pran...@xebia.com> wrote: >> About Jenkins: >> Will it be good to create separate maven profiles executed using separate >> Jenkins jobs for >> a) normal build without findbugs/checkstyle/pmd etc >> b) quality build with findbugs/checkstyle/pmd > > Is it the intended distinction between normal and quality build? if > yes, +1, seems reasonable.
