The CI is failing because maven uses TestNG instead of jUnit (log here). Consequently, instead of calling one test per job it calls all tests from the test cases which produces a timeout.
Problem identified: the sure-fire detected the TestNG dependency (Gzoltar depends on it) and use its engine. As solution, we force to use a particular test engine.
The CI is failing because maven uses TestNG instead of jUnit (log here). Consequently, instead of calling one test per job it calls all tests from the test cases which produces a timeout.