| Re: [orbit-dev] repo.eclipse.org is down? |
On Tue, 2020-05-12 at 22:45 +0200, Stephan Herrmann wrote: > Same as > https://www.eclipse.org/lists/platform-releng-dev/msg36413.html ? Now that you mention it, I did find a second example in Orbit again from roughly the same time. https://ci.eclipse.org/orbit/job/orbit-recipes/154/console The interesting part : [ERROR] Failed to execute goal on project java_cup-runtime: Could not resolve dependencies for project org.eclipse.orbit.bundles:java_cup- runtime:eclipse-bundle-recipe:0.11.20150326-SNAPSHOT: Failed to collect dependencies at org.eclipse.orbit.java-cup:java-cup- runtime:jar:0.11.20150326: Failed to read artifact descriptor for org.eclipse.orbit.java-cup:java-cup-runtime:jar:0.11.20150326: Could not transfer artifact org.eclipse.orbit.java-cup:java-cup- runtime:pom:0.11.20150326 from/to orbit-approved-artifacts ( https://repo.eclipse.org/content/repositories/orbit-approved-artifacts) : Failed to transfer file: https://repo.eclipse.org/content/repositories/orbit-approved-artifacts/org/eclipse/orbit/java-cup/java-cup-runtime/0.11.20150326/java-cup-runtime-0.11.20150326.pom . Return code is: 503 , ReasonPhrase:Service Unavailable. So either Jenkins somehow lost the ability to route traffic externally, or it was just an issue with repo.eclipse.org and Maven didn't know to try another repo when it was hit with a 503. -- Roland Grunberg