Supported tools
DevOps Intelligence supports the integration of tools including the integration of third party, data collection and management (DevOps) tools such as GitHub, CodeQL and SonarQube. This capability centralizes your view of the DevOps Intelligence lifecycle, minimizing the need to monitor multiple stations and simplifying administrative operations.
Each DevOps tool in your library can be public or private to the client. As part of the standard DevOps Intelligence offering, only the integration to the five standard public service providers (AWS, Azure, Google, IBM Cloud and Alibaba) are included.
All other service provider integrations, even if standardized and covered by best practices, require custom service engagement with a professional services team. Integration relies on REST API calls over HTTPS. In the case of public services, the communication is direct from DevOps Intelligence to the service provider API server.
In the case of private services, the communication may require an agent deployed on the client network. Interactions with DevOps tools include:
- Retrieving issue (defects, tasks) data
- Retrieving build data
- Retrieving test data
- Retrieving deployment data
- Retrieving Kubernetes cluster and container data
The Tools Configuration page allows you to onboard and manage the tools integrated with your application. Use this page to configure tool settings and onboard tools, validating connections and ensuring each tool is properly set up before use.
To onboard tools in your DevOps Intelligence application, ensure to complete the prerequisetes:
- Log in to the Kyndryl Bridge Console.
- Open the hamburger menu in the upper-left corner.
- Navigate to Services > Platform Services, Toolchain & Pipeline.
- Select DevOps Intelligence.
- In the left navigation pane, click Settings & Utilities > Tools Configuration.
This opens the Tools Configuration page, where you can manage and configure DevOps tool integrations.
For more information see, Tools configurationTools Configuration.
Pre-requisites
- Roles and permissions: Ensure you have the necessary roles and permissions within the platform to add tools, specifically the Platform Admin role. To verify your roles and permissions, refer to the Permissions section.
- Invalid credentials: An "Invalid Credentials" error may occur due to incorrect or outdated login credentials or an incorrect host configuration. To resolve this issue:
- Select Administration.
- Navigate to Developer Console.
- Under Connections, select the connection with incorrect credentials.
- View the connection details.
- Edit the connection and enter the correct credentials.
- Configuration pending: If a connection displays a "Configuration Pending" status, the setup for that connection has not been completed. Refer to the configuration section in the tools documentation below for additional guidance.
- Internal server error: If you encounter an "Internal Server Error," the service may be temporarily unavailable or the pod may be restarting. Wait a few minutes and try again.
- On Premise Proxy Adapter: If you are using a non-default DI tool with the On Premise Proxy Adapter, ensure the corresponding service is enabled in the Tenant Manager before adding the connection or service configuration. Refer to the appropriate configuration documentation for setup guidance.
Third party tools integration
DevOps Intelligence supports the integration of third party, data collection and management (DevOps) tools such as GitHub, CodeQL and SonarQube. This capability centralizes your view of the DevOps Intelligence lifecycle, minimizing the need to monitor multiple stations and simplifying administrative operations.
Each DevOps tool in your library can be public or private to the client. As part of the standard DevOps Intelligence offering, only the integration to the five standard public service providers (AWS, Azure, Google, IBM Cloud and Alibaba) are included.
All other service provider integrations, even if standardized and covered by best practices, require custom service engagement with a professional services team. Integration relies on REST API calls over HTTPS. In the case of public services, the communication is direct from DevOps Intelligence to the service provider API server.
In the case of private services, the communication may require an agent deployed on the client network. Interactions with DevOps tools include:
- Retrieving issue (defects, tasks) data
- Retrieving build data
- Retrieving test data
- Retrieving deployment data
- Retrieving Kubernetes cluster and container data
Supported tools
The platform supports the following tools:
Category | Tool | Version / Details |
|---|---|---|
Secure | Dependency Track | Default version. The platform pulls data from Dependency Track. |
Secure | CodeQL | — |
Secure | JFrog Security Essentials (Xray) | — |
Secure | Qualys Container Security Tool | — |
Secure | SonarQube | Default version. |
Develop | Atlassian Bitbucket | Cloud - API Version 2.0 / Server - API Version 1.0 |
Develop | Atlassian JIRA | API Version V2 |
Develop | AWS CodeCommit | Default version. |
Develop | AWS CodePipeline | Default version. |
Develop | AWS DevOps | Default version. |
Develop | Azure Boards and Azure Repo | API Version 7.0. Supports Azure DevOps Cloud and Azure DevOps Server. |
Develop | GitLab (Public and Enterprise) | API Version V4 |
Develop | GitHub (Public and Enterprise) | Default Version (V3) |
Build | AWS CodeBuild | — |
Build | Azure Pipelines Build | — |
Build | Jenkins | — |
Build | JFrog Artifactory | — |
Test | Azure DevOps - Test Plans Support | Default Version |
Test | Jenkins Plugin | — |
Test | SonarQube | Default Version |
Deploy | ArgoCD | — |
Deploy | AWS CloudFormation | SDK Version - 1.35.9 |
Deploy | AWS CodeDeploy | — |
Deploy | Azure Pipeline Deploy | — |
Deploy | Azure Pipelines release | — |
Deploy | Azure Resource Manager | — |
Deploy | GoCD | — |
Deploy | Google Deployment Templates | SDK Version - 0.69.1 / API Version - V2 |