管理二进制版本 [英] Managing binaries versions

查看:38
本文介绍了管理二进制版本的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在寻找有关如何管理共同构成发布版本的二进制工件的工具和建议.

I'm looking for tools and recommendations on how to manage binaries artifacts which together make up a release version.

项目如下所示:

+ Package-Version
|__ Component A-Version
|__ Component B-Version
|__ Component C-Version

可能存在更多级别,例如组件本身是由具有自己版本的子组件构建的.

More levels may exist, such that the components themselves are built from sub-components with their own versions.

目前,我们使用带有二进制文件链接的 Excel.我希望通过引入一些可以更好地管理它的简单工具来改进这一点.它应该包括一些基础知识,例如:搜索版本/子版本并定位它们在树中的位置、WEB 访问以使其易于访问并使其具有一些界面以便可以使用脚本加载新的二进制文件.此外,每个项目都需要有一些与其相关的信息,主要是发行说明.

Currently, we use an Excel with links to the binaries. I hope to improve this by introducing some simple tools that may manage it better. It should include some basics like: Searching for versions/sub-versions and locating where they are in the tree, WEB access to make it easily accessible and for it to have some interface so new binaries could be loaded using scripts. Also, each item needs to have some info related to it, mainly a Release Note.

请注意,如果重要的话,这是一个嵌入式 C/C++ 项目.

Note, this is an embedded C/C++ project if it matters.

推荐答案

推荐用于二进制文件(与特定版本的代码相关管理)的常用工件存储库是 Nexus.
对于 C++,您还可以考虑使用 Nuget 来管理这些相同的依赖项.

The usual artifact repository recommended for binaries (managed in relation with a specific version of the code) is Nexus.
For c++, you could also consider Nuget for managing those same dependencies.

在这两种情况下,想法都是在源代码控制工具中存储一个文件(例如 Nexus 的 pom.xml),该文件将指定您需要的二进制文件的确切版本(或者您构建并发布到该工件存储库)

In both cases, the idea is to store in the source control tool a file (pom.xml for Nexus for instance) which will specify the exact version of the binaries you need (or that you build and publish to that artifact repo)

通过将二进制文件置于 VCS(版本控制系统)之外,您可以确保 VCS 不会变得太大(在磁盘空间中),并且您允许 IT 生产团队(负责发布管理)访问与 IT 开发团队不同的参考(两个空间完全分离).

By keeping the binaries outside the VCS (Version Control System), you make sure the VCS doesn't get too large (in disk space), and you allow IT Production team (in charge of release management) to access a different referential than the IT Dev team (clean separation of the two spaces).

这篇关于管理二进制版本的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆