ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Павлухин Иван <vololo...@gmail.com>
Subject Re: Tests for ML using binary builds
Date Tue, 05 Mar 2019 09:20:45 GMT

If problems arise in environments different from one where usual
Ignite tests run then definitely it is a good idea to cover it. And
testing other build kinds and in other environments is a good idea as
well. But a particular problem with serialization and peer class
loading is not clear for me. Why binary builds and Docker are needed
there? Why multi JVM tests from Ignite testing framework cannot reveal
mentioned problems?

Ideally I think we should aggregate all failure reporting in common
place. And for me TC bot is the best choice. Consequently it should be
TeamCity most likely.

But all in all I think we can give it a try according to you proposal
and see how the things will go.

вт, 5 мар. 2019 г. в 11:09, dmitrievanthony <dmitrievanthony@gmail.com>:
> Hi Alexey,
> I think it's a great idea. Travis + Docker is a very good and cheap
> solution, so we could start with it. Regards the statistics, Travis allows
> to check a last build status using a badge, so it also shouldn't be a
> problem.
> Best regards,
> Anton Dmitriev.
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Best regards,
Ivan Pavlukhin

View raw message