www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philipp Ottlinger (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (INFRA-11968) Jenkins-Setup seems to contain codehaus.org / builds fail on Jenkins that work locally
Date Mon, 22 Aug 2016 20:18:20 GMT

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

Philipp Ottlinger edited comment on INFRA-11968 at 8/22/16 8:17 PM:
--------------------------------------------------------------------

[~cml][~pono] The problem is still persistent. I tried changing to other build agents (non-ubuntu)
that resulted in the same problem.

Can you somehow try to reconfigure Jenkins to use no settings.xml at all? This is how the
builds go through locally on our developer machines?!

Please check the following locations for references to codehaus.org:
*    The Maven install: ${maven.home}/conf/settings.xml
*    A user’s install: ${user.home}/.m2/settings.xml

Maybe the problem is a globally defined maven profile? Can you verify
* Per Project - Defined in the POM itself (pom.xml).
* Per User - Defined in the Maven-settings (%USER_HOME%/.m2/settings.xml).
* Global - Defined in the global Maven-settings (${maven.home}/conf/settings.xml).

Thanks again :-)



was (Author: hugo.hirsch):
[~cml][~pono] The problem is still persistent. I tried changing to other build agents (non-ubuntu)
that resulted in the same problem.

Can you somehow try to reconfigure Jenkins to use no settings.xml at all? This is how the
builds go through locally on our developer machines?!

Please check the following locations for references to codehaus.org:
*    The Maven install: ${maven.home}/conf/settings.xml
*    A user’s install: ${user.home}/.m2/settings.xml


> 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)

Mime
View raw message