Binary repository manager: Difference between revisions

Revision as of 16:51, 14 September 2019

Revision as of 13:27, 2 October 2019

Line 9:

The software and technology industry continues to change and grow, and binary repository managers are no different. They are beginning to shift towards positioning as a universal package managers.<ref>{{cite web |url= https://adtmag.com/articles/2015/09/08/jfrog-repository.aspx |title= JFrog Releases ‘Universal’ Artifact Repository |last=Waters |first= John K.| date= 8 September 2015|website=ADT Mag| publisher=Application Development Trends Magazine}}</ref> These package managers aim to standardize the way enterprises treat all package types used in the [[software development process]]. They give users the ability to apply security and compliance metrics across all artifact types. Universal package managers have been referred to as being at the center of a [[DevOps toolchain]].<ref>{{cite web |url= http://www.codeproject.com/Reference/628210/An-Overview-of-the-NuGet-Ecosystem | title=An Overview of the NuGet Ecosystem | last=Decoster | first=Xavier | date= 18 August 2013| website=CodeProject.com}}</ref>

Notable Universal package managers include:<ref>{{cite web|url=http://www.hanselman.com/blog/HowToHostYourOwnNuGetServerAndPackageFeed.aspx |title=How to host your own NuGet Server and Package Feed | last=hanselman |first=scott |date= 13 April 2015| website=Hanselman.com}}</ref>

* Apache Archiva