Alternate Sources - SonaType Nexus - Artifact Repository/Repository Management for CI/CD
Closed Pre-Solicitation Posted
- Solicitation number
- RFI_HNC_SonaType
- Agency
-
AFLCMC Joint Base San Antonio
Lifecycle Management Center, Department of Defense
- Responses due
- Set-aside
- No set-aside
Opportunity facts
- NAICS code
- 513210 Software Publishers
- Place of performance
- San Antonio, Texas 78205, United States
- Points of contact
Notice details come from SAM.gov. Updated .
About this opportunity
The Department of the Air Force Materiel Command Lifecycle Management Center Joint Base San Antonio is seeking a repository management solution to support the Development, Security and Operations (DevSecOps) Infrastructure Value Stream for the Unified Platform. The key requirements include the ability to store artifacts in AWS S3, create Docker repository mirrors, be available as a Helm chart/containerized deployment for Kubernetes, support SAML or OIDC authentication and authorization, provide role-based access control management, support various repository types, enable programmatic access, support subdomain routing and multiple authentication systems, proxy access to external repositories, and have auditable logging. This is a pre-solicitation notice, and responses to the Request for Information are due by August 8, 2024 at 11:00 AM CST. The RFI is for market research and planning purposes only, with no award or payment anticipated.
This procurement is not set-aside for any specific program. The current incumbent or contractor is not named. The potential award value or budget range is not provided. The quantity of goods or timeline for services is not specified.
Notice text
Our goal is to identify a solution that can provide a repository manager that organizes, stores and distributes development artifacts in a DevSecOps environment. The repository should provide a single point of reference for approved application containers and software artifacts for users. The repository will store, integrate with keycloak identity credential and access management (ICAM) and make available to operational organizations for evaluation and operational acceptance that have been through Continuous Integration (CI) and automated Continuous Deployment (CD) pipelines. Thereby, creating a DevSecOps compliant express lane for certification to field (CtF) and deployment of applications.
The following are some of the key characteristics that we are using to meet our organizational objectives. While this list is not exhaustive, it does provide a snapshot of some of the most important requirements for our environment:
- Ability to store artifacts in AWS S3
- Create Docker repository mirrors
- Available as a helm chart / containerized deployment for Kubernetes
- Supports SAML or OIDC authentication and authorization (Group assertions from the Idp are honored)
- Role-based access control management (RBAC) for local images
- Supports the creation and use of apt, docker, raw, maven2, rpm, pypi, npm, conda, go, gitlfs, helm, nuget, r, and yum repositories.
- Supports the use of api tokens / personal access tokens to retrieve software programmatically
- Supports the use of subdomain routing, and the use of multiple subdomains for assigning to repositories
- Support for multiple authentication systems
- Proxy access to external repositories
- Ability to record use in auditable logs so that activity can be traced to a single user
- Optimized for automation
Files
| File | Type | Posted |
|---|---|---|
| Repository Solution License RFI_07302024.pdf |
On GovTribe
Work this opportunity
- Track it in your pipeline
- Find teaming partners
- Similar opportunities
- Ask GovTribe AI about this opportunity