Binary repository manager: Difference between revisions

Revision as of 15:19, 1 May 2016

Revision as of 15:24, 1 May 2016

Line 48:

== Key features of repository Managers==

Key factors and features when considerconsidering the adoption of a package manager include:<ref>{{cite web |url= http://www.computerweekly.com/blogs/cwdn/2015/11/how-to-find-real-devops-look-for-binary-artifact-repository-control.html |title= How to find real DevOps, look for binary artifact repository control |last=Bridgewater | first=Adrian | date= 1 November 2015 |website=ComputerWeekly.com}}</ref>

*'''Caching''' – Caching simply stores local copies of packages. This increases performance for slow internet connections by allowing the user to pull from the local repository instead of externally. Caching locally allows frequently used packages to be available even during times of external repository outages.

*'''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 managermanagers 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[[high Availabilityavailability]] 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 organizationorganizational systems such as LDAP or Single Sign-onOn servers to simplify and centralize user management. This gives an enterprise granular control over who has access to vital software components.

== Tools ==