You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by GitBox <gi...@apache.org> on 2019/07/03 09:29:53 UTC
[GitHub] [camel-quarkus] ppalaga commented on issue #31: Move infinispan
integration-tests out fo core
ppalaga commented on issue #31: Move infinispan integration-tests out fo core
URL: https://github.com/apache/camel-quarkus/issues/31#issuecomment-508017386
I clearly see the benefit of testing separately and having a separate project for each component that can serve as a basic quickstart.
OTOH, each separate integration test module will prolong the build by ~2 minutes. Do we really want that? My personal limit for CI is ~40mins. Now we are at ~28mins, IIRC. So we can basically do this, but maybe for the future, we should think of some sort of policy that would keep the CI run times reasonable. Testing several extensions in one IT module is actually one possible solution, so once again the question, is it really worth splitting now?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services