Jenkinsfile: pickup results from ITs

[psiroky]

• trying to make Jenkins pick-up the IT results - currently, if some of the ITs fail, Jenkins won't pick-up the results and the build would be "green"
• not 100% sure this is the fix though, I have no way of testing this locally so will rely on the PR builds
• missing IT results can be seen for example here: https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/190/testReport/

Following this checklist to help us incorporate your
contribution quickly and easily:

• Make sure there is a JIRA issue filed
  for the change (usually before you start working on it). Trivial changes like typos do not
  require a JIRA issue. Your pull request should address just this issue, without
  pulling in other changes.
• Each commit in the pull request should have a meaningful subject line and body.
• Format the pull request title like [MNG-XXX] SUMMARY,
  where you replace MNG-XXX and SUMMARY with the appropriate JIRA issue.
• Also format the first line of the commit message like [MNG-XXX] SUMMARY.
  Best practice is to use the JIRA issue title in both the pull request title and in the first line of the commit message.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• [] Run mvn clean verify to make sure basic checks pass. A more thorough check will
  be performed on your pull request automatically.
• [] You have run the Core IT successfully.

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

• In any other case, please file an Apache Individual Contributor License Agreement.

[slawekjaranowski]

What with standard path, like **target/surefire-reports/*.xml and for failsafe?

[psiroky]

I am not sure. I assumed these patterns were tested before and the junit step was accidentally left commented out.

I think we could go with **target/surefire-reports/*.xml. It will pick-up some test results from core-it-support, but that may be desirable.

There are no failsafe-reports directories right now, but to be safe we could include those as well.

[psiroky]

I updated the PR to also pickup failsafe-reports. I haven't really tried locally, but according to https://www.jenkins.io/doc/pipeline/steps/junit/ separating the patterns with comma should work.

[psiroky]

I noticed there is also Jenkinsfile.its which seems unused? Should it be just removed, or am I missing the usage somewhere?

[slawekjaranowski]

@psiroky Thanks for PR, I will try it on branch in maven repo ... PR from fork are not build by jenkins

[slawekjaranowski]

Suppressed by #953