Binary repository manager: Difference between revisions

Revision as of 19:18, 17 April 2019

Revision as of 14:23, 22 April 2019

Line 64:

*'''Retention policies''' - Repository managers can be used and configured to support organization purging policies to ensure reasonable disk space usage. Local repositories for third party artifacts may also be purged after not being used by any release for a specified time.

*'''License filtering''' - Third party artifacts may be subject to approval processes due to licensing and legal issues. Package managers allow for the restriction of only approved artifacts into deployment.

*'''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., Maintainingmaintaining 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 user management. This gives an enterprise granular control over who has access to vital software components.