与nuget的联系还是人工的? [英] nexus or artifactory with nuget?
问题描述
我正在尝试将体面的参考管理引入我的组织.之前曾经在Maven中使用过Nexus，但我知道它比在本地构建一切的方法要优越得多.因为这是一个.Net商店，所以我想使用NuGet代替Maven.我知道二进制存储库将是最重要的方面，但是没有在二进制存储库中托管NuGet存储库的经验.
I am trying to introduce decent reference management to my organisation. Having used Nexus with Maven before, I know it to be far superior to the method of building everything locally. As this is a .Net shop I want to use NuGet instead of Maven. I know the binary repository will be the most important bit to get right, but have no experience of hosting a NuGet repository in a binary repository.
在这种情况下，是否有任何理由支持Nexus或Artifactory?如果有什么区别，我们将svn作为Jenkins作为CI.
Is there any reason to favour Nexus or Artifactory in this situation? We are using Jenkins with svn as our CI, if that makes any difference.
推荐答案
这是我们上次比较Artifactory和Nexus中的NuGet支持时发现的结果(免责声明-我与JFrog在一起):
This is what we found out last time we compared the NuGet support in Artifactory vs. Nexus (disclaimer - I'm with JFrog):
-
在Artifactory中，NuGet支持已自然地集成到产品中，这使管理变得更加容易-只需将本地存储库标记为已启用NuGet或为远程回购设置远程URL.多个NuGet存储库可以轻松地聚集在单个虚拟NuGet存储库中-与Artifactory中任何其他存储库相同的方法；在Nexus中，您将需要定义一种新的存储库类型，设置一个新的专用安全领域，并且如果您需要一个现有的存储库来同时满足NuGet请求，则必须为其添加一个特殊的外观.这是Nexus中的一种通用方法，其中每种新型存储库(例如P2)都需要进行多级配置更改.
In Artifactory the NuGet support is naturally integrated into the product, which makes management much easier - just mark a local repository as NuGet enabled or set the remote URL for a remote repo. Multiple NuGet repositories can be easily aggregated under a single virtual NuGet repo - same approach used with any other repo in Artifactory; In Nexus, you will need to define a new type of repository, set up a new dedicated security realm, and if you need an existing repository to also answer NuGet requests you have to add a special facade to it. This is a general approach in Nexus where every new type of repository (such as P2) requires multi-level configuration changes.
Nexus UI中绝对没有集成NuGet软件包.您甚至无法搜索NUGet工件，这对于管理和维护至关重要(这就是为什么仅从Visual Studio进行搜索是不够的).这主要是由于Nexus高度面向Maven和Maven布局. 在Artifactory中，您可以像其他任何工件一样搜索和管理NuGet软件包.您可以在用户界面中通过nuspec元数据> 查看信息，甚至进行钻取向下查看NuPkg程序包下单个文件的内容，并检查它们的内容.
There is absolutely no integration for NuGet packages in the Nexus UI. You cannot even search for NUGet artifacts, which is crucial for management and maintenance (which is why searching only from Visual Studio cannot be enough). This is mainly due to the fact that Nexus is highly oriented towards Maven and the Maven layout; In Artifactory, you can search and manage NuGet packages like any other artifacts. You can view information from the nuspec metadata in the UI and even drill down into the content of individual files under a NuPkg package, and inspect their content.
Artifactory中的安全集成也更容易-无需手动生成特殊密钥，而密钥只是用户名和密码或安全密码的组合.如果您希望用户的NuGet密码与Artifactory的MS-AD/LDAP集成同步，那就太好了；在Nexus中，NuGet使用隔离的安全领域.
Security integration is also easier in Artifactory - there is no need to manually generate a special key, but the key is just the combination of the username and password or a secure password. This is great if you want your users NuGet passwords to be synced with Artifactory's MS-AD/LDAP integration; In Nexus NuGet uses an isolated security realm.
Artifactory实现了完整的NuGet搜索范围，包括更深奥但有用的用例，而底层实现则结合使用了内存缓存和持久的，预先计算的可搜索属性，以确保NuGet即使对于庞大的存储库，查询也非常快速且可扩展；不确定Nexus是否使用类似的优化方法.
Artifactory implements the complete range of NuGet searches, including the more esoteric but useful use-cases, and the underlying implementation uses a combination of in-memory caches and persistent, pre-calculated, searchable properties to make sure NuGet queries are very fast and scalable even for a huge repository; Not sure if Nexus uses similar optimizations.
我希望能帮上忙.
PS. NuGet支持是Artifactory Pro版本的一部分，并且免费包含在Nexus OSS中
PS. NuGet support is part of the Pro versions of Artifactory, and included for free in Nexus OSS since september 2014.
这篇关于与nuget的联系还是人工的?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
