All geek questions in one place

Versioning executable files

I am looking for tools and guidelines for managing binary artifacts that together make up the release version.

The project is as follows:

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

Other levels may exist, so the components themselves are created from subcomponents with their own versions.

We are currently using Excel with links to binary files. I hope to improve this by introducing a few simple tools that can better handle this. It should include some basics, such as: searching for versions / sub-versions and finding places where they are in the tree, accessing the WEB to make it easily accessible and for it to have some interface so that new binaries can be downloaded using scripting. In addition, each item should have some information related to it, mainly a release note.

Please note that this is a built-in C / C ++ project, if that matters.

+4
source share
2 answers

The usual artifact repository recommended for binary files (managed with respect to a specific version of the code), Nexus .
For C ++, you can also consider Nuget to manage the same dependencies.

In both cases, the idea is to store a file (for example, pom.xml for Nexus) in the original management tool that will indicate the exact version of the binaries you need (or you create and publish an artifact for this repository)

By storing binary files outside of VCS (version control systems), you will make sure that VCS does not get too large (on disk) and you let the IT Production team (responsible for release management) access a different command than the IT Dev team (pure separation of two spaces) .

+3
source

You can think and try Mercurial with the Large File Extension (precaution "... is considered a function of last use")

Some large files, not so obvious details described in

+1
source

Source: https://habr.com/ru/post/1435214/

More articles:


All Articles