Bugzilla – Full Text Bug Listing
| Summary: | deploy CI build results from hudson.eclipse.org to a maven repo | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Jan Sievers <jan.sievers> |
| Component: | Tycho | Assignee: | Project Inbox <tycho-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | benjamin.jung, gernot, igor, karsten.thoms, t-oberlies, thanh.ha |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 360944 | ||
| Bug Blocks: | |||
|
Description
Jan Sievers
see also http://www.sonatype.com/people/2011/10/publishing-your-artifacts-to-the-central-repository/ For Tycho release artifacts, the easiest way is probably to go through oss.sonatype.org as described in [2]. For snapshots, we can either use maven.eclipse.org or oss.sonatype.org (for consistency with releases). It is theoretically possible to setup synching of release artifacts from maven.eclipse.org to the central repo, but this is something Eclipse webmaster needs to negotiate with Sonatype. From what I understand, this only makes sense if large number of Eclipse projects are planning to produce Maven artifacts and deploy them to central. For the few Eclipse projects that currently do this, going through one of existing repositories is easier. [2] https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide created bug 360944 to find out how to deploy snapshots to maven.eclipse.org *** Bug 363696 has been marked as a duplicate of this bug. *** (In reply to comment #4) > *** Bug 363696 has been marked as a duplicate of this bug. *** changed title to make it more findable I got the ball rolling with oss.sonatype.org https://issues.sonatype.org/browse/OSSRH-2537. In the meantime I've re-enabled Sonatype internal Tycho build to deploy to https://repository.sonatype.org/content/repositories/snapshots/. I'll turn it off again once we have oss.sonatype.org repo setup for Tycho. Forgot to mention, to use Tycho snapshot build add the following to your (parent) pom.xml
<pluginRepositories>
<pluginRepository>
<id>tycho-snapshots</id>
<url>https://repository.sonatype.org/content/repositories/snapshots/</url>
</pluginRepository>
</pluginRepositories>
(In reply to comment #6) > I got the ball rolling with oss.sonatype.org In the light of issues with maven.eclipse.org like bug 365727 and bug 360944, +1 for sonatype repo for now if it's OK from eclipse IP point of view. Did you check this with Wayne? Deploying to oss.sonatype.org directly from eclipse hudson apparently violates vendor neutrality [1]. This bugzilla will have to wait until there is existing Maven repository hosting infrastructure at eclipse. [1] http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg06861.html (In reply to comment #7) > Forgot to mention, to use Tycho snapshot build add the following to your > (parent) pom.xml Just for the reference: This workaround no longer works. Igor announced the new Sonatype-provided CI build result location in this message [1] Jan is driving the Eclipse infrastructure based solution, but this is currently blocked by bug 360944. [1] http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00421.html move all bugs to post 0.14.0 With the progress on repo.eclipse.org (see bug 394792 and wiki documentation [1]), we should now be able to get this working. [1] http://wiki.eclipse.org/Services/Nexus#Deploying_artifacts_to_repo.eclipse.org @Thanh we would need a new repo created https://repo.eclipse.org/content/repositories/tycho-snapshots/ to deploy tycho SNAPSHOTS to. Note that for releases we still have to deploy to maven central but let's keep this separate for now. (In reply to comment #12) Note to self: Igor wants to have changes to the Tycho CI delivery proposed and discussed on the dev&user lists first. (In reply to comment #13) > @Thanh > > we would need a new repo created > > https://repo.eclipse.org/content/repositories/tycho-snapshots/ > > to deploy tycho SNAPSHOTS to. > > Note that for releases we still have to deploy to maven central but let's > keep this separate for now. I created the repo tycho-snapshots as requested. I also created a group "tycho" but it only points to tycho-snapshots. https://repo.eclipse.org/content/groups/tycho/ (In reply to comment #14) > (In reply to comment #12) > Note to self: Igor wants to have changes to the Tycho CI delivery proposed > and discussed on the dev&user lists first. I strongly believe changes that affect all/most tycho developers and users must be discussed on the mailing lists first. This is not specific to CI or any particular area, this applies to any significant change in tycho dev process or tycho behaviour. deployment on http://ci.tesla.io:8080/view/Tycho/job/tycho/ has started to fail again for authentication reasons since yesterday 10 am. I guess we can get the same, if not better, service level on repo.eclipse.org Due to repeated problems with the snapshot deployment to oss.sonatype.org (bug 435050), we are now promoting the snapshots deployed by our CI job at Eclipse [1] as the official ones: <pluginRepositories> <pluginRepository> <id>tycho-snapshots</id> <url>https://repo.eclipse.org/content/repositories/tycho-snapshots/</url> </pluginRepository> </pluginRepositories> So I suppose we can close this issue. [1] https://hudson.eclipse.org/tycho/view/CI/ (In reply to comment #18) > https://repo.eclipse.org/content/repositories/tycho-snapshots/ I've also configures this URL as the source for Tycho snapshots in the Tycho Extras build: http://git.eclipse.org/c/tycho/org.eclipse.tycho.extras.git/commit/?id=3b7c1181d85759c60e95143e691f7aea9e26d00a |