Hi,
as far as I know Sonar is not communicating directly with the JaCoCo agents. You run a regular build wich creates JaCoCo exec files in your build workspace. The sonar plugin then uploads coverage data (among other data) to the sonar server via HTTP requests. Please contact the Sonar project how to configure the server connections in your case.
Regarding JaCoCo we decided some time ago that the agent should not get an http interface (dependencies, security etc).
Regards,
-marc
> On 21. Dec 2018, at 12:08,
nkkost...@gmail.com wrote:
>
> Hi, I am working within a large branch of the German government. We are migrating our Build Pipeline from Bitbucket + Jenkins2 + Sonar + Virtual Server Instances to Bitbucket + Jenkins2 + Sonar + Marathon Cloud (Docker Containers). We use Jacoco to track the code coverage of both unit and Contract Driven Tests. In order to get the coverage shown in Sonar, Jacoco is triggered within our Jenkins through the Jacoco Maven Plugin. Now we face a challenge since the Marathon Cloud is "hidden" behind a couple of load balancers, which are configured to allow only HTTP Requests. The problem is that Jacoco uses pure TCP Sockets. Do you have plans on adding HTTP support? If not, I will be happy to contribute to the Jacoco project and it myself. Can you guide me through that?
>
> --
> You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
jacoco+un...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/jacoco/e38eea30-eae3-4510-95b6-60548b01f4eb%40googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.