[MNG-6726] Integration tests should use non empty MAVEN_OPTS. Jenkinsfile and 'core-it-suite' should accept custom MAVEN_OPTS from developers and their CLI.

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Component/s: Integration Tests
• Environment: Jenkins CI, development environment too
• Assignee: Robert Scholte
• Reporter: Tibor Digana
• Created: 30/Jul/19 10:57
• Updated: 28/Mar/20 20:55
• Resolved: 28/Mar/20 20:55

Description

Using non-empty MAVEN_OPTS (dummy prop) to prevent from merging env vars in child integration test with env vars from (caller) parent process.

The child env var takes the precedence in this fix.
Merging env vars between parent/child processes is performed in maven-shared-utils:
see Commandline#addSystemEnvironment() and see the line
Properties systemEnvVars = CommandLineUtils.getSystemEnvVars().

With this fix we can freely use the MAVEN_OPTS within our integration tests.

Issue Links

• relates to: MNG-6714 Broken build with 3 failed ITs in master