Difference between revisions of "Binary repository manager"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
Tags: Mobile web edit, Mobile edit |
||
| Line 30: | Line 30: | ||
* {{package managers}} | * {{package managers}} | ||
* {{SCA}} | * {{SCA}} | ||
| + | * {{CI}} | ||
[[Category:DevOps]] | [[Category:DevOps]] | ||
Revision as of 05:39, 1 March 2020
This article is a Draft. Help us to complete it.
- Apache Archiva
- Azure Artifacts
- CloudRepo
- JFrog Artifactory (2008-2009)
- GitLab (2011, GitLab itself)
- GitHub
- Sonatype Nexus repository manager
- Pulp, open source.
Characteristics:
- high availability
- multi-site replication
- disaster recovery
- scalability.
Activities
See also
- Container Registry: JFrog Container Registry, AWS ECR, Azure container registry, VMware Harbor Registry, Google Cloud Registry, Amazon Elastic Container Registry (ECR), GitLab container registry,
crane, gcr.io, ghcr.io - Binary repository manager: JFrog Artifactory, GitLab, GitHub and Nexus repository manager
- Package managers: dpkg, APT, RPM, YUM, DNF, homebrew, pkgutil, opkg, Helm, pkg and snap, npm, Aptitude, alien, Conan, CRAN, Chocolatey, NuGet, PackageKit, Wajig, pacman, PIP, Apache Ivy, List packages, List files in packages, Spack
- Software Composition Analysis (SCA): Flexera, FOSSA, GitLab Ultimate, JFrog Xray, Snyk, Sonatype, Synopsys: Black Duck, Veracode, WhiteHat Security, WhiteSource, Bill of Materials (BOM), Semgrep, Clair
- Continuous integration (Continuous delivery): GitLab CI, TeamCity, Travis CI, Jenkins, CloudBees, AWS CodePipelines, Azure Pipelines, XebiaLabs, Codefresh, GitHub, Pipeline, CircleCI, JFrog Pipelines, Concourse CI, Dagger, Bitbucket Pipelines, Buildkite, Google Cloud Build
Advertising:
