Details
Task
Resolved
Major
Description
From my findings, it looks like the problem is the settings.xml file.
E.g. this "works" -> https://travis-ci.org/alb-i986/jbehave-core/builds/57723534
this does not -> https://travis-ci.org/alb-i986/jbehave-core/builds/57725840
The latter fails because of these:
[WARNING] Could not validate integrity of download from http://maven.jenkins-ci.org/content/repositories/releases/org/apache/maven/plugins/maven-surefire-plugin/2.17/maven-surefire-plugin-2.17.jar: Checksum validation failed, no checksums available [WARNING] Checksum validation failed, no checksums available for http://maven.jenkins-ci.org/content/repositories/releases/org/apache/maven/plugins/maven-surefire-plugin/2.17/maven-surefire-plugin-2.17.jar
The thing is that that URL does not exist:
$ curl -I http://maven.jenkins-ci.org/content/repositories/releases/org/apache/maven/plugins/maven-surefire-plugin/2.17/maven-surefire-plugin-2.17.jar
HTTP/1.1 404 Not Found
Date: Thu, 09 Apr 2015 00:15:17 GMT
Server: nginx
Content-Type: application/json;charset=ISO-8859-1
X-Artifactory-Id: oss1-use-1d-jenkinsci
Via: 1.1 maven.jenkins-ci.org
Set-Cookie: SERVERID=local; path=/
I'm not sure if it's a bug to report to travis, or something wrong with our settings.xml.
Any thoughts?
BTW, the former "works" (i.e. can download deps) but fails because it needs to know the custom maven repo which happens to be defined in settings.xml. Kind of a recursive issue!
Activity
Alberto Scotto
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
From my findings, it looks like the problem is the settings.xml file.
E.g. this works -> https://travis-ci.org/alb-i986/jbehave-core/builds/57723534 this does not -> https://travis-ci.org/alb-i986/jbehave-core/builds/57725840 The latter fails because of these: {code} [WARNING] Could not validate integrity of download from http://maven.jenkins-ci.org/content/repositories/releases/org/apache/maven/plugins/maven-surefire-plugin/2.17/maven-surefire-plugin-2.17.jar: Checksum validation failed, no checksums available [WARNING] Checksum validation failed, no checksums available for http://maven.jenkins-ci.org/content/repositories/releases/org/apache/maven/plugins/maven-surefire-plugin/2.17/maven-surefire-plugin-2.17.jar {code} The thing is that that URL does not exist: {code} $ curl -I http://maven.jenkins-ci.org/content/repositories/releases/org/apache/maven/plugins/maven-surefire-plugin/2.17/maven-surefire-plugin-2.17.jar HTTP/1.1 404 Not Found Date: Thu, 09 Apr 2015 00:15:17 GMT Server: nginx Content-Type: application/json;charset=ISO-8859-1 X-Artifactory-Id: oss1-use-1d-jenkinsci Via: 1.1 maven.jenkins-ci.org Set-Cookie: SERVERID=local; path=/ {code} I'm not sure if it's a bug to report to travis, or something wrong with our settings.xml. Any thoughts? |
From my findings, it looks like the problem is the settings.xml file.
E.g. this "works" -> https://travis-ci.org/alb-i986/jbehave-core/builds/57723534 this does not -> https://travis-ci.org/alb-i986/jbehave-core/builds/57725840 The latter fails because of these: {code} [WARNING] Could not validate integrity of download from http://maven.jenkins-ci.org/content/repositories/releases/org/apache/maven/plugins/maven-surefire-plugin/2.17/maven-surefire-plugin-2.17.jar: Checksum validation failed, no checksums available [WARNING] Checksum validation failed, no checksums available for http://maven.jenkins-ci.org/content/repositories/releases/org/apache/maven/plugins/maven-surefire-plugin/2.17/maven-surefire-plugin-2.17.jar {code} The thing is that that URL does not exist: {code} $ curl -I http://maven.jenkins-ci.org/content/repositories/releases/org/apache/maven/plugins/maven-surefire-plugin/2.17/maven-surefire-plugin-2.17.jar HTTP/1.1 404 Not Found Date: Thu, 09 Apr 2015 00:15:17 GMT Server: nginx Content-Type: application/json;charset=ISO-8859-1 X-Artifactory-Id: oss1-use-1d-jenkinsci Via: 1.1 maven.jenkins-ci.org Set-Cookie: SERVERID=local; path=/ {code} I'm not sure if it's a bug to report to travis, or something wrong with our settings.xml. Any thoughts? BTW, the former "works" (i.e. can download deps) but *fails* because it needs to know the custom maven repo which happens to be defined in settings.xml. Kind of a recursive issue! |
Unbelievable! I got a green build on travis!!!
https://travis-ci.org/alb-i986/jbehave-core/builds/61058951
:O
Show
Alberto Scotto
added a comment - Unbelievable! I got a green build on travis!!!
https://travis-ci.org/alb-i986/jbehave-core/builds/61058951
:O
Alberto Scotto
added a comment - Unbelievable! I got a green build on travis!!!
https://travis-ci.org/alb-i986/jbehave-core/builds/61058951
:O Pulled with thanks:
Show
Mauro Talevi
added a comment - Pulled with thanks:
https://github.com/jbehave/jbehave-core/pull/81/
Mauro Talevi
added a comment - Pulled with thanks:
https://github.com/jbehave/jbehave-core/pull/81/ Mauro Talevi
made changes -
| Resolution | Fixed [ 1 ] | |
| Fix Version/s | 3.10 [ 20672 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
The jenkins maven repo is only for Jenkins artifacts. The surefire plugin is found in Maven Central. If not found in one repo, it'll look it up in another.
The build works with settings.xml provided unless there are network issues preventing correct download.
Travis has been known to have connection issues.