| Summary: | Upload problems to OSSRH | ||
|---|---|---|---|
| Product: | Community | Reporter: | Karsten Thoms <karsten.thoms> |
| Component: | CI-Jenkins | Assignee: | CI Admin Inbox <ci.admin-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | frederic.gurr, mikael.barbero, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Karsten Thoms
The best practice to deploy artifacts to OSSRH is to use org.sonatype.plugins:nexus-staging-maven-plugin (see https://central.sonatype.org/pages/apache-maven.html). Please, give it a try and report if you still face issues. The nexus-staging-plugin does not help in this context. The deployment of the EMF artifacts is using an *existing* p2 repo, and the POMs are created with the CBI aggregator. It does not allow to extend the POM by additional plugins (or I do not know how). The challenge is to make the contents of the Maven repo produced by CBI available to Maven Central. This requires to use a command line call to deploy single artifacts. However, the actual problem seems to be solved. I tried the build again and the upload speed was now OK and the build was successful. There was some networking issue. Since it is working now, I'll close this ticket. I'm again experiencing severe problems. Upload takes ages. This used to work in the meantime, so I have to assume some infrastructure problem. Could you please take a look? https://ci.eclipse.org/emf/job/publish-maven/67/console Can you raise a ticket on the OSSRH JIRA about this (and link to it here)? We are not aware of any issues on our side at the moment. Will do the next time I face that issue. |