refactor: merge dockerpool into "core" to prepare release (#953)

repairnator/README.md

@@ -16,7 +16,6 @@ This directory contains the different subfolders:
 Repairnator is decomposed in 6 different modules: 
   - repairnator-core: contains shared elements for all other elements, it can be also use to generate Google Spreadsheets Credentials
   - repairnator-scanner: scan automatically Travis Build and produce metrics and list of build ids (only for Bears)
-  - repairnator-dockerpool: this part can be used to create a pool of docker containers to launch taking as input a list of build ids
   - repairnator-pipeline: it is the engine of Repairnator. Given a build id this part, compile, test and repair it, gathering data on it, and push on Github and on MongoDB
   - repairnator-realtime: inspects in realtime the builds from Travis (typically every minute)
 
@@ -29,11 +28,6 @@ The following process is generally used.
 First, `repairnator-pipeline` is built using shared element from `repairnator-core` and a docker image is created. 
 
 If the user wants to follow and repair in realtime the builds procuced by Travis, then she should use `repairnator-realtime`.
-The component is build using elements from `repairnator-core` and `repairnator-dockerpool`: the docker image previously created will be used automatically for each failing build.
 
-Then if the user wants to repair scanned builds on a timerange, she should use `repairnator-scanner` and then `repairnator-dockerpool`.
-First she built and launch `repairnator-scanner`, using a list of Github project as input, and a list of build ids will be produced.
-Then she can build and launch `repairnator-dockerpool` against this list of build ids: the previously created docker image will be then used.
-
-Those process can be automatically triggered using the scripts given in `scripts` directory.
+Those processes can be automatically triggered using the scripts given in `scripts` directory.
 

repairnator/pom.xml

@@ -70,7 +70,6 @@
         <module>repairnator-pipeline</module>
         <module>repairnator-core</module>
         <module>repairnator-scanner</module>
-        <module>repairnator-dockerpool</module>
         <module>repairnator-realtime</module>
         <module>build-rainer</module>
     </modules>

repairnator/repairnator-realtime/pom.xml

@@ -11,7 +11,7 @@
 
     <dependencies>
         <dependency>
-            <artifactId>repairnator-dockerpool</artifactId>
+            <artifactId>repairnator-core</artifactId>
             <groupId>fr.inria.repairnator</groupId>
             <version>3.1-SNAPSHOT</version>
         </dependency>
@@ -76,4 +76,4 @@
             </plugin>
         </plugins>
     </build>
-</project>
+</project>

repairnator/scripts/config/repairnator.cfg

@@ -61,7 +61,6 @@ HUMAN_PATCH=0 # Test the human patch for check branches ?
 ### Versions
 
 SCANNER_VERSION=LATEST
-DOCKERPOOL_VERSION=LATEST
 REALTIME_VERSION=LATEST
 PIPELINE_VERSION=latest
 CHECKBRANCHES_VERSION=LATEST
@@ -83,7 +82,6 @@ ROOT_BIN_DIR=$HOME_REPAIR/bin/ # The directory will be created if it does not ex
 ### Binary paths
 REPAIRNATOR_RUN_DIR=$ROOT_BIN_DIR`date "+%Y-%m-%d_%H%M"` # Where to put executables used (will be created automatically and deleted)
 REPAIRNATOR_SCANNER_DEST_JAR=$REPAIRNATOR_RUN_DIR/repairnator-scanner.jar
-REPAIRNATOR_DOCKERPOOL_DEST_JAR=$REPAIRNATOR_RUN_DIR/repairnator-dockerpool.jar
 REPAIRNATOR_CHECKBRANCHES_DEST_JAR=$REPAIRNATOR_RUN_DIR/repairnator-checkbranches.jar
 REPAIRNATOR_REALTIME_DEST_JAR=$REPAIRNATOR_RUN_DIR/repairnator-realtime.jar