I_4 20240606 1605 5000174533 SF1014 RFI Amend 1.pdf

CBJ RFI Ques ons:

1. Provide detail to describe your tool critical elements that satisfy the following IRS tool requirements:

a. Continuous Integration Management Software for automated building and testing of code by project teams.

b. Supports Open-Source Jenkins (OSJ) automation servers to enable software deployment by project teams.

c. Centralized Jenkins Deployment and Configuration for administrators to manage users and add-ins and overlook the state of systems, servers, and software from a central dashboard to manage the enterprise pipeline.

d. Jenkins Connector Support for third party Tools Integration for diverse needs of IRS project teams

e. Jenkins Cloud Hosting to support projects deploying to cloud environments.

f. Advanced Security Connectors to ensure integration capabilities with required Cyber tools:

SonarQube, AppScan, NexusIQ, Qualys, Splunk

g. Release Orchestration to support automated deployment through Ansible Automation Platform

h. Enterprise Jenkins Scalability to ensure ability of the enterprise pipeline to handle growth and meet increased demand.

i. Integration with Source Code Management tools like Rational Team Concert/Enterprise

Workflow Management, GitHub etc.

j. Running Jenkins on-prem on Virtual Machines as well as on container platforms like OpenShift

k. Integration with other enterprise systems using REST based APIs.

2. Describe your method to integrate with the agency’s release orchestration tool (Ansible Automation

Platform integration with source code management tools (EWM/GitHub), and integration with the agency ticketing system for IT Service Management (ServiceNow) for full traceability and audit history, as well as logging and verifying approvals that are mandated as part of every deployment of code to production.

3. Describe how your tool will accomplish IRS IT Cyber Security requirements integrating with

AppScan, NexusIQ, SonarQube and Qualys to enforce code quality and prevent security issues from being deployed to production.

4. Describe how your company can complete any needed tool customization to align with existing CICD pipeline requirements such as security connectors, tool incorporation with existing pipeline users and integration to various enterprise DevSecOps solutions in place such as Ansible, ServiceNow, Rational Team Concert Enterprise Workflow Management tool suite, GitHub Enterprise, Nexus, LoadRunner, SoapUI, and Selenium.

5. Describe your process to transition from the CICD CBJ pipeline to the new vendor tool solution and the migration of 160+ core tax processing projects while supporting without disruption a minimum of 5,000 daily Jenkins integration executable jobs:

6. Describe your process to transition CJB CICD Groovy pipeline scripts and their supporting libraries for 400+ repositories, without project disruption, and training protocol to educate developers on the scripting language for the new tool. Must be completed within 180 days of the contract execution and within a $3,937,500 budget.

7. During the 180-day Cloudbees Jenkins (CBJ) tool transition to the new tool period, describe your ability to support without disruption a minimum of 5,000 daily Jenkins integration executable jobs without disruption to 160+ application projects or cause a critical outage. Each 160+ IRS applications generate and maintain hundreds of Jenkins pipelines.