[
https://issues.apache.org/jira/browse/KAFKA-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978916#comment-14978916
]
Rajini Sivaram commented on KAFKA-2644:
---------------------------------------
[~ijuma] All the SASL tests are now passing in the Confluent build
(http://jenkins.confluent.io/job/kafka_system_tests_branch_builder/135/console).
But the tests now take an extra 2 hours to run. The current PR runs the
console consumer sanity test, all replication tests and all benchmarks using
both SASL_PLAINTEXT and SASL_SSL. I think there is value in running the sanity
test and replication tests using both the SASL protocols. Would it make sense
to restrict the number of benchmarks run with SASL? Maybe only run
_test_producer_and_consumer_ and _test_end_to_end_latency_? Since all the tests
are passing, it would be a trivial change to remove the tests that are not
required.
> Run relevant ducktape tests with SASL_PLAINTEXT and SASL_SSL
> ------------------------------------------------------------
>
> Key: KAFKA-2644
> URL: https://issues.apache.org/jira/browse/KAFKA-2644
> Project: Kafka
> Issue Type: Sub-task
> Components: security
> Reporter: Ismael Juma
> Assignee: Rajini Sivaram
> Priority: Critical
> Fix For: 0.9.0.0
>
>
> We need to define which of the existing ducktape tests are relevant. cc
> [~rsivaram]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
