[hibernate-dev] HHH-12172 - Bintray v. OSSRH

Sanne Grinovero sanne at hibernate.org
Fri Jan 12 06:59:46 EST 2018


Personally I'm neutral. I surely wouldn't want to manage our own
Artifactory, but since JFrog will do that I'm not concerned about the
platform management being horrible.

Artifactory looks better, OSSRH has the benefit of possibly having
better integration with Maven.

There are some benefits on staying to JBoss's nexus though; not
expressing a strong opinion but let's clarify these.

# Stats
We need download statistics, which I understand they all offer, but an
absolute number is not as useful as being able to compare the numbers
in one dashboard across various others of our projects.
Also not looking forward to have to login to multiple systems to gather it all.

# Quality control of artifacts
I'm understanding that JBoss Nexus does several strict validations on
our poms; sure they have been in the way as it's not nice to see such
failures *during* a release but there's an upside to them as well.
AFAIK OSSRH also has similar rules, but the JBoss team one has
different ones, plus a deal with Sonatype to deem our stuff good
"pre-approved" so we don't have to satisfy the Sonatype rules too.

# Signing
Also I'm understanding that to release on OSSRH we need to sign all
artifacts; not a bad idea but it's quite more papework and key
management. Such paperwork is handled for us by the JBoss Nexus team.
We'd need to install GPG on our release servers, get a organization
RSA key signed, and people stubbornly releasing manually will have to
create a key each, and have it approved by Sonatype.

Not against migrating if this is what you all want - just making sure
we're keeping these into account.

Thanks,
Sanne


On 12 January 2018 at 02:47, Brett Meyer <brett at hibernate.org> wrote:
> Sorry for the late and probably irrelevant response...
>
> We're using an in-house Artifactory instance at a gig and it's been
> trash.  I can't speak to the UI or management end, nor Bintray, but
> Artifactory's platform doesn't seem as polished (can't believe I just
> said that) or stable (can't believe I said that either) as Nexus (what
> is happening).
>
> I use OSSRH for some minor projects and have generally had decent luck
> -- including a few interactions with the support team that went well.
> OSSRH != JBoss Nexus, although I definitely understand the wounds...
>
>
> On 12/19/17 8:34 AM, Steve Ebersole wrote:
>> HHH-12172 is about moving away from the JBoss Nexus repo for publishing our
>> artifacts.  There is an open question about which service to use instead -
>> Sonatype's OSSRH (Nexus) or JFrog's Bintray (Artifactory).
>>
>> Personally I think Artifactory is far superior of a UI/platform.  We all
>> know Nexus from the JBoss deployment of it, and we have all generally had
>> nothing good to say about it.
>>
>> But I am wondering if anyone has practical experience with either, or knows
>> persons/projects tyay do and could share their experiences.  E.g., even
>> though I prefer Bintray in almost every regard, I am very nervous that it
>> seems next to impossible to get help/support with it.  The same may be true
>> with OSSRH - I don't know, hence why I am asking ;)
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev


More information about the hibernate-dev mailing list