I'm attempting to create a travis build to run this android gradle project.
Travis is erroring on this java related SSL exception. I can't figure out what I'm missing. Any help would be greatly appreciated. I've attached the link to the build, with the full error and build info.
$ ./gradlew clean build
Downloading https://services.gradle.org/distributions/gradle-2.2.1- all.zip
Exception in thread "main" java.lang.RuntimeException: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative DNS name matching services.gradle.org found.
at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:78)
at org.gradle.wrapper.Install.createDist(Install.java:47)
at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:129)
at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:48)
Here is the full build.
Travis Build
Here's the cause:
http://discuss.gradle.org/t/urgent-ssl-apache-configuration-for-services-gradle-org-is-bad/8808
Workaround would be to modify gradle/wrapper/gradle-wrapper.properties with distributionUrl using http instead of https. Until they fix the problem.
Related
this is came from yesterday onwards, when i run the maven for docker project i am getting
Failed to execute goal org.wso2.maven:mi-container-config-mapper:5.2.35:config-mapper-parser (config-mapper-parser) on project ESBDockerExporter: Exception while parsing the deployment.toml file
this is the plug-in i added in docker pom.xml
There is a known issue that happening due to the new HTTPS template URL. So with the new URL HTTPS config, the older "mi-container-config-mapper" plugin has some issues.
So in order to correct this update the version in the k8s project pom file as below.
<artifactId>mi-container-config-mapper</artifactId>
<version>5.2.35</version>
I am getting the following error on Jenkins when I try to do a gradle build of my code along with Junit tests:
Caused by: java.lang.IllegalStateException: java.lang.IllegalStateException: Logback configuration error detected:
ERROR in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Failed to create parent directories for xxxxxx
Basically Jenkins is trying to look for the directory specified in the logback.xml, but it doesn't have permission to build the directory structure.
I am using the Jacoco plugin with Jenkins for generating test reports.
Any help to resolve this issue is very much appreciated.
Thanks
I resolved the issue by using
#TestPropertySource(properties = "logging.config=classpath:logback.xml")
where in the logback-spring.xml was ignored during Jenkins build.
I'm having some trouble with my jenkins build - I'm trying to generate some sources based on several json files. No problem on my lokalhost, but my Jenkins build always fails with this exception:
[ERROR] Failed to execute goal org.jsonschema2pojo:jsonschema2pojo-maven-plugin:0.4.23:generate (DriversGeneration) on project DKVGatewayRestClient: Execution DriversGeneration of goal org.jsonschema2pojo:jsonschema2pojo-maven-plugin:0.4.23:generate failed: Unrecognised URI, can't resolve this: http://gateway-int.dkv-euroservice.com/metadatastore/1.0.0.1-SNAPSHOT/mds/com/dkv/shared/drivers/getCardList.json: Connection timed out -> [Help 1]
Basically it says that http://gateway-int.dkv-euroservice.com/metadatastore/1.0.0.1-SNAPSHOT/mds/com/dkv/shared/drivers/getCardList.json is not a valid URI, but this definatly is not the case. As said, my localhost can work with this URI without any problems - browser and maven build work exactly as expected. Even using requesting this URL via curl on my Jenkins server works perfectly fine. Just the Jenkins build constantly fails. Have already restartet Jenkins but no difference ...
Can anyone give me a hint? Thanks in advance and regards. Sebastian
i have a maven2 project which is built periodically by jenkins. The bad thing about it ... it won´t build anymore.
I´m not sure what has changed, because i don´t have any tickets in the code itself or jenkins configuration, but strange as it is..... the local build works.
Normally that would hint on a configuration problem in jenkins, but the error in jenkins is:
[ERROR] XJC while parsing schema(s) file:/global/contint/build_server/jenkins/jobs/ERIC_E4N%20Continuous-Trunk-Check/workspace/Eric4N-publishing-xsd/src/main/resources/E4N_E4D_InterfaceSalesAllowanceDoType.xsd[76,14]: org.xml.sax.SAXParseException: 'SalesAllowanceDoType' is already defined
Locally I don´t get this error....
Any clues where I could continue my search ?
Thanks alot and Greetings !
I'm currently reading the book 'Jenkins Continuous Integration Cookbook', and I came across this error after building a project on Jenkins:
ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users#googlegroups.com
java.lang.NullPointerException
at java.io.File.<init>(File.java:239)
at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58)
at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41)
at hudson.FilePath.act(FilePath.java:1001)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:604)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:567)
at hudson.model.Run.execute(Run.java:1604)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:506)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:246)
project=hudson.maven.MavenModuleSet#68f55ff2[A]
project.getModules()=[]
project.getRootModule()=null
I'm confused why I'm getting this, since my Java code is all autogenerated via Maven, and my tests in HTML format. I was able to successfully build the code using maven, before placing a directory with /src and pom.xml as it's children onto bitbucket.
Any ideas why this error is showing? Any advice will be appreciated.
Adding the rest of the error logs below (couldn't before because I was getting formatting errors).
FATAL: null
java.lang.NullPointerException
at java.io.File.<init>(File.java:239)
at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58)
at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41)
at hudson.FilePath.act(FilePath.java:1001)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:604)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:567)
at hudson.model.Run.execute(Run.java:1604)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:506)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:246)
According a similar bug report (but not exactly the same) I guess that your problem may be caused by a wrong configuration in Jenkins.
I suggest you to check the MAVEN_HOME used by Jenkins (i.e. check that it is really a MAVEN_HOME directory and is the correct maven version)