Content deleted Content added
No edit summary |
No edit summary |
||
Line 1:
A '''binary repository manager''' is a software tool designed to help maintaining a store of [[binary files]] produced in software development, often storing metadata where it was built out of, and its dependencies. The repository manager helps to provide a central URL to download binary dependencies to developers and continuous builds. To make this download efficient for most binary formats a table of contents of all binary artifacts stored is provided to allow a client program to calculate the dependency graph without contacting the server. A notable exception is maven which does not have a table of contents.
== Introduction ==
Line 69 ⟶ 67:
*'''High availability''' - Since a binary repository manager maintains all the development dependencies, it is vital to always maintain access to these artifacts. Any down-time of the binary repository manager can halt development with all the significant consequences to the organization. A [[high availability]] instance allows an enterprise to overcome the risk associated with downtime, through automatic failover. This is achieved by having a redundant set of repository managers work against the same database and file storage, maintaining enterprise-wide stability and performance at all times.
*'''User restrictions''' - Repository managers can be integrated with other organizational systems such as [[LDAP]] or [[single sign-on]] servers to simplify and centralize [[computer access control|user management]]. This gives an enterprise granular control over who has access to vital software components.
==References==
|