Hello Maxim, > Why do you think that splitting the checkstyle build is better option than fixing code style issues reporting by the checkstyle plugin? Why do you think that Ilya talks that code style errors should not be fixed?
It looks weird to me that we do not even start the tests if check style plugin reports violations. Why can't this check be done in parallel with the tests and reported by mtcga bot? Why this check is so important? Why do you think it is more important than all other tasks/tests? Thanks, Slava. пн, 6 июл. 2020 г. в 20:34, Maxim Muzafarov <mmu...@apache.org>: > Hello Ilya, > > Why do you think that splitting the checkstyle build is better option > than fixing code style issues reporting by the checkstyle plugin? > > On Mon, 6 Jul 2020 at 19:43, Ilya Kasnacheev <ilya.kasnach...@gmail.com> > wrote: > > > > Hello! > > > > I have just noticed today that Checkstyle will fail Apache Ignite build: > > > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_BuildApacheIgnite/5443282?buildTab=log&focusLine=3&linesState=683.4289 > > > > This means that I have completely lost an option to run tests against > pull > > requests by new contributors - they usually compile but will not pass > > Checkstyle. That's a blocker. > > > > Can we please split Checkstyle as a separate build which is triggered > with > > Run All? > > I think we even have > > > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CheckCodeStyle?mode=builds#all-projects > > > > WDYT? > > > > Regards, > > -- > > Ilya Kasnacheev >
