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] [Commented] (INFRA-11968) Jenkins-Setup seems to contain codehaus.org / builds fail on Jenkins that work locally
Date Tue, 24 May 2016 21:57:13 GMT

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

Philipp Ottlinger commented on INFRA-11968:

Thanks for the reply and help [~pono] - it seems that codehaus is not contacted due to update
[WARNING] Failure to transfer org.apache.tamaya:buildconfigurations:0.3-incubating-SNAPSHOT/maven-metadata.xml
from http://nexus.codehaus.org/snapshots/ was cached in the local repository, resolution will
not be reattempted until the update interval of codehaus-snapshots has elapsed or updates
are forced. Original error: Could not transfer metadata org.apache.tamaya:buildconfigurations:0.3-incubating-SNAPSHOT/maven-metadata.xml
from/to codehaus-snapshots (http://nexus.codehaus.org/snapshots/): nexus.codehaus.org: Name
or service not known

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

View raw message