Git和Nexus的区别？ [英] Difference between Git and Nexus?

问题描述

我似乎无法找到Git和 Nexus 之间的区别。这两者是可比的吗？

有两个参考：

• one（ Git ）是版本控制的源代码参考（具有合并，分支，标签）
其他（ Nexus ）是一个神器参考对于任何交付（二进制或不）

$ b

参考数据库也不同：






• Git拥有自己的内部存储库存储机制


• Nexus仅仅是一个具有命名约定（group.artifact.version）的共享目录集合。 >
  如什么是存储库：存储在已定义目录结构中的二进制软件工件和元数据的集合。
  




这个想法是对于可以经常生产的大型交付来说，将它们存储在Nexus中非常容易（您可以轻松地清除它们： cd + rm ），而不是它们的版本（这使得像Git这样的DVCS回购方式太快而无法轻松克隆）。





他们的目标是不同的，正如我在下面解释的那样：







• 不同版本控制系统如何处理二进制文件？ 存储.jar文件的最佳实践VCS（SVN，Git，...）


• 在源代码管理项目中使用源代码受控库





您在Git中管理您的代码，以及在Nexus中构建。




I can't seem to find what the difference is between Git and Nexus. Are the two comparable?

解决方案

There are both referential:

• one (Git) is a source referential for version control (with features like merging, branching, tags)
• the other (Nexus) is an artifact referential for any delivery (binaries or not)

The referential database differs also:

• Git has its own internal repository storage mechanism
• Nexus is simply a collection of shared directories with a naming convention ( group.artifact.version ).
  As described in "What is a repository": a collection of binary software artifacts and metadata stored in a defined directory structure.

The idea is that, for large deliveries that can be produced quite often, it is much easier to store them in Nexus ( you can clean them easily enough: cd + rm ), as opposed to version them ( which makes a DVCS repo like Git way too big way too fast to be cloned easily ).

So their goals are different, as I explain in:

• "How do different version control systems handle binary files?"
• "Best practice to store .jar files in VCS (SVN, Git, …)"
• "Using source controlled libraries in source controlled projects"

You manage what you code in Git, and what you build in Nexus.

这篇关于Git和Nexus的区别？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！