[
https://issues.apache.org/jira/browse/CASSANDRA-14428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460574#comment-16460574
]
Marcus Eriksson commented on CASSANDRA-14428:
---------------------------------------------
bq. Can we run eclipse warnings inside the unit test job so we don't have to
spin up the environment and build Cassandra again? That would save a bit less
than two minutes. You could have it bail out if it's not container index 0 or
just have all of them run it.
I did it this way since it would avoid having to re-run all unit tests just to
check that the {{eclipse-warnings}} error is fixed - this way it would only
start all containers running unit tests if {{eclipse-warnings}} is successful,
not sure I understand how we could save any time since we don't build an extra
time?
> Run ant eclipse-warnings in circleci
> ------------------------------------
>
> Key: CASSANDRA-14428
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14428
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Major
> Fix For: 4.x
>
>
> We should run ant eclipse-warnings in circle-ci
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
