You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The existing scheduled Kubernetes integration tests check that the Java ITs passed when run against an actual cluster of HDFS/Zookeeper/Accumulo. To ensure Kerberos support is throughly tested, a second version of these tests could be created to run them against a Kerberised cluster as well.
The scheduled integration tests only run on develop at the moment, they will need to also run on v2-alpha as the Kerberos work has not yet been merged into develop.
The text was updated successfully, but these errors were encountered:
Since this issue was originally written the integration tests have moved to using Docker Compose and the v2-alpha branch is no longer relevant. Scheduled tests are probably not needed for Kerberos, they just need to be run for each release.
These tests will be run using the same approach as #266, but with Kerberos configuration files.
* Add docker compose and config files for Integration tests with Kerberos
* Improve dockerfile apt install commands
This prevents getting stuck on installer messages which prompt for user input
The existing scheduled Kubernetes integration tests check that the Java ITs passed when run against an actual cluster of HDFS/Zookeeper/Accumulo. To ensure Kerberos support is throughly tested, a second version of these tests could be created to run them against a Kerberised cluster as well.
The scheduled integration tests only run on
develop
at the moment, they will need to also run onv2-alpha
as the Kerberos work has not yet been merged intodevelop
.The text was updated successfully, but these errors were encountered: