[MPOM-294] Remove surefire from Maven site reports

[slawekjaranowski]

No description provided.

[michael-o]

@hboutemy

[hboutemy]

what is the problem with this report?

I find the timing of each test in the report particularly interesting https://maven.apache.org/plugins/maven-deploy-plugin/surefire-report.html

[slawekjaranowski]

The same information we have on CI
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-deploy-plugin/job/master/lastCompletedBuild/testReport/org.apache.maven.plugins.deploy/

The biggest problem for this report is that test phase is triggered during site build ... and can take a long time.

We was start to validate site build on GH, Jenkins and want to improve it.

[hboutemy]

perhaps CI configuration should not be the same than release-time -Preporting

[michael-o]

I agreee with @hboutemy I don't see a huge reason to run reporting with CI.

[slawekjaranowski]

The most problematic and what should be tested is javadoc build, reports. But javadoc reports is in reporting profile.

[hboutemy]

why not just create a separate ci profile?

[slawekjaranowski]

we should run at least one build site (on os and jdk) with reporting profile to be sure that all plugins used in reporting profile still working.

[slachiewicz]

Knowing that we would have new pom soon - any decisions here?

[Tibor17]

hm, I do not understand his change.
The CI result is used to fail due to Socket time out. The same has happened in the latest surefire result vote. The build was red, we tried to restart the build for 3 days, and finally the build has got green at the end of the Vote.

Instead of removing the surefire report, we should adjust the process and the template should be changed and a new entry should be added along with Site link, SHA512, etc.

If one report is going to be removed, there should be some substitution but mandatory substitution done in prior.

This would improve the process while you prepare the release on your own, but this should not be all. This PR seems to be incomplete.

[slachiewicz]

https://maven.apache.org/wagon/surefire-report.html.

[Tibor17]

@slachiewicz
So, this zero report told me that we should ask the developer if the unit tests are really not interesting to write.

[slachiewicz]

https://maven.apache.org/surefire/surefire-report.html i would say that report is empty becouse running test was disabled while site publish runs

[hboutemy]

-1