On my machine a full mvn clean install takes 55 minutes.
As an experiment I put all MapReduce job tests for all clustering algorithms on ignore. This reduces the build to 45 minutes. There are a lot of these long running tests in the project.
What about creating a separate maven profile for the nightly build that run all MapReduce job tests? For this we have to move these MapReduce tests
to separate classes with a naming convention such as *JobTest or *IntegrationTest and add some maven configuration.