maven-soapui-extension-plugin icon indicating copy to clipboard operation
maven-soapui-extension-plugin copied to clipboard

Travis CI build: fix failing tests relying on maven options

Open redfish4ktc opened this issue 11 years ago • 3 comments

Starting from Travis build 179 (runned on 2013-11-24), all integration tests relying on maven options (tests skipping execution by setting MAVEN_OPTS to -Dmaven.test.skip=true in the maven invoker configuration). There was no error on the build 178 (runned on 2013-11-07) and the only change between these 2 builds is the version in the pom.xm file.

The Travis build environment has changed on the 20th of November so this could be part of the issue. The java stack rollout includes jdk upgrade and switching to maven 3.1.1

I've not been able to reproduce the issue both on a Windows OS local box, nor on CloudBees - cloudbees build uses maven 3.1.1, oracle jdk 1.7.0_45 on a Linux box as Travis CI does.

redfish4ktc avatar Nov 28 '13 05:11 redfish4ktc

The following tests fail

mock_goal/skip_execution/soapui-extension-skip-system-property/pom.xml
mock_goal/skip_execution/soapui-oss-skip-system-property/pom.xml
mock_goal/skip_execution/soapui-pro-skip-system-property/pom.xml
test_goal/skip_execution/soapui-extension-skip-system-property/pom.xml
test_goal/skip_execution/soapui-oss-skip-system-property/pom.xml
test_goal/skip_execution/soapui-pro-skip-system-property/pom.xml

redfish4ktc avatar Nov 28 '13 11:11 redfish4ktc

Other users have experienced broken builds since the Travis build environment update. See travis-ci #1689 to test the workaround

redfish4ktc avatar Feb 18 '14 00:02 redfish4ktc

Seems fixed now on Travis environment as the build has been green for a while

redfish4ktc avatar Mar 08 '17 11:03 redfish4ktc