Community
Participate
Working Groups
I know it's Neon.1 release day today, but still our internal Hudson jobs shouldn't fail reading from download.eclipse.org ? Especially as the external bandwidth is throttled based on what I heard recently ? Please let us know what can be done to avoid such errors: https://hudson.eclipse.org/tcf/job/tcf-master-4.7/ Maybe the internal infrastructure for builds could be separate from the external infrastructure for downloads ?
Earlier today we had this error, so builds have been failing for us for 6 hours today: [ERROR] Plugin org.eclipse.cbi.maven.plugins:eclipse-jarsigner-plugin:1.1.2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.eclipse.cbi.maven.plugins:eclipse-jarsigner-plugin:jar:1.1.2: Failure to transfer org.eclipse.cbi.maven.plugins:eclipse-jarsigner-plugin:pom:1.1.2 from https://repo.eclipse.org/content/repositories/cbi-releases/ was cached in the local repository, resolution will not be reattempted until the update interval of cbi has elapsed or updates are forced. Original error: Could not transfer artifact org.eclipse.cbi.maven.plugins:eclipse-jarsigner-plugin:pom:1.1.2 from/to cbi (https://repo.eclipse.org/content/repositories/cbi-releases/): Failed to transfer file: https://repo.eclipse.org/content/repositories/cbi-releases/org/eclipse/cbi/maven/plugins/eclipse-jarsigner-plugin/1.1.2/eclipse-jarsigner-plugin-1.1.2.pom. Return code is: 503 , ReasonPhrase:Service Temporarily Unavailable. -> [Help 1]
This seems to have been only an intermittent error. Please reopen if it happens again.
