infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (INFRA-17046) Empire-db Jenkins Build keeps failing (for about 3 months)
Date Fri, 21 Sep 2018 15:54:00 GMT

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

Chris Lambertus edited comment on INFRA-17046 at 9/21/18 3:53 PM:
------------------------------------------------------------------

The protocol error is probably due to SSL changes at maven central which no longer support
ancient and insecure java versions. Either update your build to use Java 8+ or try specifying
-Dhttps.protocols=TLSv1.2 as an mvn parameter.




was (Author: cml):
The protocol error is probably due to SSL changes at maven central which no longer support
ancient and insecure java versions. Either update your build to use Java 8+ or try specifying
-Dhttps.protocols=TLSv1.2



> Empire-db Jenkins Build keeps failing (for about 3 months)
> ----------------------------------------------------------
>
>                 Key: INFRA-17046
>                 URL: https://issues.apache.org/jira/browse/INFRA-17046
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Rainer Döbele
>            Priority: Major
>
> Dear Infra,
> we had an issue with hard disk space on the Jenkins machine (INFRA-17041) that you have
resolved. However we are still having build problems.
> Since about 3 months we're getting a maven build error on Jenkins without having made
any significant changes to the maven configuration.
> We always get the following error:
> [ERROR] Plugin com.mycila.maven-license-plugin:maven-license-plugin:1.9.0 or one of its
dependencies could not be resolved: Failed to read artifact descriptor for com.mycila.maven-license-plugin:maven-license-plugin:jar:1.9.0:
Could not transfer artifact com.mycila.maven-license-plugin:maven-license-plugin:pom:1.9.0
from/to central (https://repo.maven.apache.org/maven2): Received fatal alert: protocol_version
-> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
> For testing I have disabled the maven-license-plugin but the I got the following:
> [ERROR] Plugin org.apache.maven.plugins:maven-javadoc-plugin:2.10.3 or one of its dependencies
could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-javadoc-plugin:jar:2.10.3:
Could not transfer artifact org.apache.maven.plugins:maven-javadoc-plugin:pom:2.10.3 from/to
central (https://repo.maven.apache.org/maven2): Received fatal alert: protocol_version ->
[Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
> When I disabled this one I got:
> [ERROR] Plugin org.apache.felix:maven-bundle-plugin:2.5.0 or one of its dependencies
could not be resolved: Failed to read artifact descriptor for org.apache.felix:maven-bundle-plugin:jar:2.5.0:
Could not transfer artifact org.apache.felix:maven-bundle-plugin:pom:2.5.0 from/to central
(https://repo.maven.apache.org/maven2): Received fatal alert: protocol_version -> [Help
1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> Locally the project builds fine.
> I have no idea what is going on and how to go about it.
> Can you help with this issue?
> Latest build with error:
> https://builds.apache.org/blue/organizations/jenkins/Empire-db%20snapshot/detail/Empire-db%20snapshot/942/pipeline
> Last successful build:
> https://builds.apache.org/blue/organizations/jenkins/Empire-db%20snapshot/detail/Empire-db%20snapshot/926/pipeline



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message