Feat: parallelize dspot on Kubernetes (#802)

[henry-lp]

Hi, this PR contains necessary files for deploying Dspot on Kubernetes in reference to this issue (#802). For more details please check out the readme at this link :) . Tell me also if there are any problems to fix.

[coveralls]

Pull Request Test Coverage Report for Build 2093

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 98 unchanged lines in 9 files lost coverage.
• Overall coverage increased (+0.2%) to 84.514%

---

Files with Coverage Reduction	New Missed Lines	%
dspot/src/main/java/eu/stamp_project/test_framework/implementations/NoneTestFrameworkSupport.java	1	20.0%
dspot/src/main/java/eu/stamp_project/test_framework/implementations/junit/JUnit3Support.java	3	92.86%
dspot/src/main/java/eu/stamp_project/test_framework/implementations/AssertJTestFramework.java	4	50.0%
dspot/src/main/java/eu/stamp_project/utils/options/AmplifierEnum.java	5	83.33%
dspot/src/main/java/eu/stamp_project/test_framework/TestFramework.java	7	91.86%
dspot/src/main/java/eu/stamp_project/utils/options/Configuration.java	11	68.0%
dspot/src/main/java/eu/stamp_project/dspot/DSpot.java	12	86.9%
dspot/src/main/java/eu/stamp_project/utils/options/JSAPOptions.java	26	81.05%
dspot/src/main/java/eu/stamp_project/utils/program/InputConfiguration.java	29	89.85%

Totals
Change from base Build 2065:	0.2%
Covered Lines:	4928
Relevant Lines:	5831

---

💛 - Coveralls

[danglotb]

Looks good to me.

However, I don't get the point with the two Travis. Where is the difference between without_dspot and with_dspot? Both traces look exactly the same.

Thank you!

[henry-lp]

Hi @danglotb , ah sorry I might have missed out elaborating that. The difference is in the pom.xml file . I assume that if people know about this technology then they would add dspot as maven dependency rather than using a jar file :) . The difference between the pom files is down below to spare you the trouble looking up.

   <plugins>
        <plugin>
          <groupId>eu.stamp-project</groupId>
          <artifactId>dspot-maven</artifactId>
          <version>2.1.0</version>
          <configuration>
            project=.
            targetModule=.
            src=src/main/java
            testSrc=src/test/java
            javaVersion=8
          </configuration>
        </plugin>
    </plugins>

Cheers :)

[danglotb]

Hello @tailp

Okay, I saw the difference.

But If I get it right, the Travis build should trigger dspot on your project, right? But I can't see this execution.

Thus, IHMO your dspot's configuration is probably wrong since it looks like you are defining properties (that should be defined in a separate file .properties) in your pom.

Best

[henry-lp]

Hi @danglotb :),

An example procedure can be like this for the stand-alone dspot without repairnator:

• A dev or some other programs can submit a travis build id on the ActiveMQ using the script "publisher.py" in this folder

• Then since we have several dspot instances listening to this queue, it will pull the travis build id from the queue and fetch the repository (with correct git branch ofcourse) related to that build id.

• Then it will run the usual Dspot on the cloned repo as a subprocess (more details in this script and submit the output files on mongodb when done.

If this is paired together with repairnator, you can add a gitwebhook on the repo and when travis build is done running it will trigger the monitor to analyze the repo and fetch the recent build Id which either is sent to repairnator if the travis build failed for repairing or further amplication using Dspot upon success. The design for this monitor is in here

I need to discuss this with @monperrus later about whether we should modify the repairnator scanner for submitting build id also for Dspot or create a completely new dspot scanner to fetch build id, but that's just an add on and for now everything is functioning fine :) .

Regard the configuration, do you mean my "with_dspot" travis branch pom.xml ?. I just followed your doc and configured it that way and it seems to be working just fine for me running dspot as maven plugin. Maybe I misunderstood something, please enlighten me if that's the case :) .

Best

[monperrus]

Thanks for the progress. I would suggest to make baby pull requests. The first one could only contain a Dockerfile in order to run Dspot through docker. WDYT?

[henry-lp]

Sorry for the late answer :) . It will be done with a new fork and in a new PR .

[monperrus]

This continues in #841