Bug 507519 - Provide Eclipse Stable Releases on Bintray
Summary: Provide Eclipse Stable Releases on Bintray
Status: CLOSED WONTFIX
Alias: None
Product: CBI
Classification: Technology
Component: artifact repository (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P4 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: CBI Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 507480 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-11-15 02:11 EST by Peter Kirschner CLA
Modified: 2020-06-12 12:30 EDT (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Kirschner CLA 2016-11-15 02:11:01 EST
Eclipse is offering the Foundation and Mirror servers as facilities for consumers. P2 is using these mirrors auto-magically, which is great, but...

if I want to comsume the Platform Release or Simultaneous Release Repo from other tools than p2, I need to specify one dedicated server.
So it would be great to have the official stable Eclipse releases hosted on JFrog Bintray.
This would allow to consume the bundles from one server, which is using the underlying CDN to get the best mirror server. The consuming tool can reference then the one and only bintray location and get the best mirror server.

Spreading the Eclipse release bundles would become easier and more stable for non P2 users. And finally it would reduce the traffic on the Eclipse Main Servers.
Comment 1 Michael Vorburger CLA 2016-11-15 06:28:53 EST
*** Bug 507480 has been marked as a duplicate of this bug. ***
Comment 2 David Williams CLA 2016-11-15 12:20:58 EST
As far as I can tell, this "cost money", right? Therefore adding webmaster to CC since I think it would only be feasible if, in the end, it could replace something Eclipse is currently doing, and thus save them money. 

What are the "other tools" you are using instead of p2. I mean, they really are p2 repositories, not intended for "other tools" so you use-case would be interesting to know about just from an academic point of view. 

Is this for an Eclipse project? Or, something "some company" wants? If the latter, as far as I know, companies can arrange to "redistribute" Eclipse artifacts (within the constraints of the EPL, of course, which is not hard). 

Thanks in advance for answering my questions.
Comment 3 Peter Kirschner CLA 2016-11-16 01:17:16 EST
Bintray is offering free plans for OpenSource projects. 
Up to 1 TB/M downloads, 10 GB/M Storage and CDN support.
So that should be sufficient for the start.

Regarding the tools...
I'm using bndtools, oomph and p2 ant tasks. In all of them I specify only one source location for the Eclipse repositories.

Purpose is open source tooling...
- Eclipse RCP templates for bndtools
- Oomph product and project setups for OSS

Regarding the "redistribute" Eclipse artifacts ...
I already thought of uploading the Eclipse artifacts myself and investigated on that. It would be feasible, but having it officially done by the foundation is more reliable and reputable.
Comment 4 Wayne Beaton CLA 2016-11-16 16:21:12 EST
(In reply to Peter Kirschner from comment #3)
> I already thought of uploading the Eclipse artifacts myself and investigated
> on that. It would be feasible, but having it officially done by the
> foundation is more reliable and reputable.

FWIW, while the Eclipse Foundation does have some staff engaged on the CBI project, most of what gets done around here is done by community members like yourself.
Comment 5 Peter Kirschner CLA 2016-11-17 05:16:38 EST
(In reply to Wayne Beaton from comment #4)

So I would appreciate to contribute the upload script, but the Eclipse Foundation should create the Bintray Account/User.
And I must admit that I haven't worked with the CBI yet.
Is this article still valid or is it outdated?
https://www.eclipse.org/community/eclipse_newsletter/2013/august/article3.php

regards,

peterkir
Comment 6 Mikaël Barbero CLA 2020-06-12 12:30:35 EDT
I'm going to close this one as it has raised little interest from the community and I don't plan to work on this.