Multiphase Onboarding for Technical Services
Multi-Phase Technical Service Onboarding provides a unified experience for onboarding technical services across multiple phases. Users can select tool resources, associate them with applications, review onboarding readiness, submit the onboarding request, and monitor the results through a single workflow.
- Multi-Phase Technical Service Onboarding offers the following capabilities:
- Onboard applicable technical services across multiple phases through one workflow.
- Review previously attempted and completed onboarding runs.
- Review existing tool configurations for an application.
- Monitor processing progress and review onboarding results.
The unified workflow reduces the need to configure the same technical service separately for each applicable phase.
Onboard a Technical Service using Multiphase Onboarding
- From the Kyndryl Bridge main menu, go to Services → Platform Services → Tool Chain & Pipeline → DevOps Intelligence.
- From the local navigation, go to Settings & Utilities → Application Configurations.
- Select the Multiphase Onboarding tab.
- The Multi-Phase Technical Service Onboarding page opens. Complete the six-step workflow:
Step 1: Connection
- From Connection Type, select the tool you want to onboard: GitHub, JFrog, Azure DevOps or Argo CD.
JFrog supports multiple levels of nesting. If onboarding has already been completed at a child or nested level, onboarding at the corresponding parent level is not allowed. Continue onboarding at the applicable child level.
- From Connection, select the applicable configured connection.
- Click Validate connection.
- Click Next.
Step 2: Tools
- Select the applicable tool capabilities or phases. Available options depend on the selected tool; applicable options may be selected by default and can be cleared when they are not required.
- Click Next.
Step 3: Repositories
- Select the applicable resources for the tool. Available resources can include repositories, modules, submodules, projects or area paths.
- Select up to 100 repositories to onboard.You can select one or more available child resources when applicable.
- Assign application bindings using the application column for each repository, or use the dropdown menu at the top to apply a binding to all selected repositories.
When assigning application bindings, you might encounter repository errors that require additional configuration. Review the error and complete the corresponding action before proceeding:
- Missing Webhooks: The Missing Webhooks error applies to GitHub and Azure DevOps (ADO). DevOps Intelligence (DI) relies on webhooks after the initial synchronization is complete. If this error appears, verify that webhooks are enabled at the source for the GitHub repository or ADO project you are onboarding.
- Missing Tool Configuration: The Missing Tool Configuration error indicates that the required tool is missing from the DI application tool metadata configuration for the applicable phase. Edit the application, go to the applicable phase, add the required tool and verify that its status is Configured.
- Click Next.
Onboarding run information is persisted so that you can return later to review previously attempted and completed activities.
Step 4: Review
- Review the selected resources, application bindings, applicable phases and onboarding readiness. Ready to onboard indicates that the required configuration is available. If the required tool configuration is missing, return to the application and add the tool for the applicable phase before continuing.
- Click Submit.
Step 5: Processing
Monitor processing progress. When backend processing is complete, progress reaches 100%. You can leave the page and return later to review the results.
Step 6: Results
Review the onboarding results. Items that were already configured can be skipped during the onboarding operation. UseTools configuration Tool Configuration to review resources already onboarded for an application, and select the connection to review processing information, including errors and processed entities.