Cloud Services

DevOps Intelligence

GitHub Actions configuration
Published On Oct 28, 2024 - 11:00 AM

GitHub Actions configuration

Learn how to integrate GitHub Actions in DevOps Intelligence to enable insights into your Build and Deploy workflows.
GitHub Actions enables the automation of tasks and processes in their Build and Deploy workflows, providing insights into these phases of the DevOps lifecycle. Developers can define custom workflows using YAML syntax, which can be triggered by events such as code pushes, pull requests, or scheduled intervals. DevOps Intelligence captures all workflows in Github Actions and retrieves them.
This data is then processed and displayed in the form of graphs and tables on the Build and Deploy pages.

Integration of GitHub Actions in DevOps Intelligence

DevOps Intelligence pulls data from GitHub Actions such as Build and Deploy details, including its unique identifier, status, time stamp, duration, and cause. Use the following procedure to onboard GitHub Actions.
  1. Create a Personal Access token (PAT) to authenticate GitHub services to access resources:
    • From GitHub homepage, go to User Settings, select Developer settings and then Personal Access Tokens. Select
      Generate new token
       and make sure the token has read permissions on the organization/repo.
  2. Create a GitHub Actions connection using the PAT previously created. For additional details, refer to the connection page.
  3. From DevOps Intelligence, go to
    Settings & Utilities
    . Select
    Tools Configuration
  4. Select
    Add Configuration
     and complete corresponding information:
    1. Tool engine: Select GitHub actions from the dropdown menu.
    2. Connection: Select the connection from the dropdown menu.
    3. Organization: Select your project from the dropdown menu.
    4. Repository name: Select your repository name from the dropdown menu.
    5. Additional configurations: Customize the terminologies that will display DevOps Intelligence dashboards for
      Passed
      ,
      Failed
       and
      In Progress
       statuses.
  5. Click
    Add Configuration
    .
The successful configuration will be displayed in the configuration table. For additional information, refer to the module page..

Configuring GitHub Actions

To complete the integration of GitHub Actions, you must complete a configuration process. Kyndryl supports two different configuration processes only one of which your organization has subscribed. If your organization was onboarded before 6 June, 2024, you are subject to the legacy process (legacy customers). If your organization was onboarded on 6 June 2024 or after, you are subject to the new process (recent customers). Refer to the appropriate document in the following list:
The configuration mechanisms that require these processes are in a transition phase driven by the fact that each tool must be individually adapted for the new mechanism, which is more efficent than the legacy mechanism. Both processes are supported until the transition of all supported tools from the old mechanism to the new mechanism is complete.
Do you have two minutes for a quick survey?
Take Survey