Feature #4277
closed
Move built hadoop artificats to download URL
Added by Noah Watkins about 11 years ago.
Updated about 11 years ago.
Description
We are at the point now where we are building some useable jar files that we'd like to reference from the Hadoop documentation page along with installation notes.
I recall that ceph.com/debian is fed by gitbuilder output, and i'm wondering what we can do along those lines for hadoop?
The output of the gitbuilders are staged to gitbuilder.ceph.com, the release process (different set of scripts) produces the repos that are available on ceph.com. If the output of the hadoop build is debian and rpm packages then those could be added to a repo on ceph.com, and folks can use apt-get or yum to install them. If they are just jar files or the like, it may make sense to add them to /ceph.com/downloads with an appropriate naming convention. The release process is documented at http://ceph.com/docs/master/dev/release-process/ which may be helpful.
If you have an idea about how folks will want to be downloading and installing the artifacts, that might determine the best choice.
Thanks for the info Gary! Let me do a little bit more research on how users want to obtain the artifacts. I think that download is fine, but I'm not sure about pkg mgmt or Java specific repositories like Maven Central.
- Status changed from New to In Progress
- Assignee set to Anonymous
As a starting point, let's post this on the download page as stand-alone jar files. I'll take ownership of doing that and then return this ticket to unassigned so that we can circle back and sort out if we want to do something above and beyond that ( Maven, debs, etc.).
I have a documentation branch pushed up that is waiting for the URLs. Let me know what those are and I can integrate them.
- Assignee deleted (
Anonymous)
For now, we're manually posting Hadoop bindings to http://ceph.com/download/. I'll close this for now and we can revisit this when we need to go to a automatic deployment between gitbuilders and the download website. We'll need to sort out versioning at that point (or sooner).
- Status changed from In Progress to Closed
Also available in: Atom
PDF