Ahem, it's embarassing... :-). The IT I added in the patch is failing, but in its very beginning when it's trying to decrypt the dummy password in the src/it/settings.xml [1] I looked into the issue, and I'm not sure how to solve it (just re-checked, the IT works fine on my machine).
Any idea of how to solve this? The simplest solution might be to simply get rid of the <server> block here [2], but as I cannot test it on the target CI system, would prefer not to propose random commits to try and kill the issue :-). Or maybe this is something that's solveable on the Jenkins job configuration side? Thanks Cheers [1] https://builds.apache.org/job/maven-scm/ws/maven-scm-plugin/target/it/scm-741-validate-scm-url-matches-working-copy/build.log [2] https://github.com/apache/maven-scm/pull/8/files#diff-1154d0ea8f6b5143a055345bf1fae166R24 ---------- Forwarded message ---------- From: Apache Jenkins Server <[email protected]> Date: 2014-02-13 17:31 GMT+01:00 Subject: maven-scm - Build # 827 - Failure To: [email protected], [email protected] The Apache Jenkins build system has built maven-scm (build #827) Status: Failure Check console output at https://builds.apache.org/job/maven-scm/827/ to view the results.
