[jira] [Commented] (INFRA-11968) Jenkins-Setup seems to contain codehaus.org / builds fail on Jenkins that work locally

["Philipp Ottlinger (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/INFRA-11968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320065#comment-15320065 ] 

Philipp Ottlinger commented on INFRA-11968:
-------------------------------------------

[~ipv6guru] the latest failures are due to syntax errors in settings.xml - did you change something?

{code}
Caused by: hudson.remoting.ProxyException: hudson.maven.MavenEmbedderException: 1 problem was encountered while building the effective settings
[FATAL] Non-parseable settings /home/jenkins/.m2/settings.xml: unexpected character in markup % (position: START_TAG seen ...</username>\n     <password><%... @14:18)  @ /home/jenkins/.m2/settings.xml, line 14, column 18

Caused by: hudson.remoting.ProxyException: org.apache.maven.settings.building.SettingsBuildingException: 1 problem was encountered while building the effective settings
[FATAL] Non-parseable settings /home/jenkins/.m2/settings.xml: unexpected character in markup % (position: START_TAG seen ...</username>\n     <password><%... @14:18)  @ /home/jenkins/.m2/settings.xml, line 14, column 18
{code}

Node was:
jenkins-test-341
https://builds.apache.org/job/Tamaya-Site-Master/30/consoleFull


> Jenkins-Setup seems to contain codehaus.org / builds fail on Jenkins that work locally
> --------------------------------------------------------------------------------------
>
>                 Key: INFRA-11968
>                 URL: https://issues.apache.org/jira/browse/INFRA-11968
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>         Environment: https://builds.apache.org/job/Tamaya-Javadoc-Master/
> https://builds.apache.org/job/Tamaya-Site-Master/
>            Reporter: Philipp Ottlinger
>
> A Tamaya-Javadoc build - that works perfectly fine locally - fails on CI due to references to codehaus.org.
> Since codehaus.org is down a while the question is how does this configuration come into CI. A local build without any references to Codehaus repository works fine.
> The build runs daily and fails, please have a look on the logs:
> {code}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-cli) on project tamaya-code: failed to get report for org.codehaus.mojo:findbugs-maven-plugin: Plugin org.codehaus.mojo:findbugs-maven-plugin:3.0.1 or one of its dependencies could not be resolved: Could not transfer artifact org.apache.tamaya:buildconfigurations:jar:0.3-incubating-SNAPSHOT from/to codehaus-snapshots (http://nexus.codehaus.org/snapshots/): nexus.codehaus.org: Unknown host nexus.codehaus.org -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR]   mvn <goals> -rf :tamaya-code
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)