Onboard to DevOps Change Velocity using Workspace

  • Release version: Washingtondc
  • Updated August 1, 2024
  • 4 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Onboard to DevOps Change Velocity using Workspace

    Onboarding to DevOps Change Velocity allows users to integrate their DevOps toolchain and automate change requests directly from the DevOps Change Workspace. Users can onboard as a DevOps admin, tool owner, or app owner, each with specific roles and actions to follow.

    Show full answer Show less

    Key Features

    • Roles and Responsibilities:
      • DevOps Admin: Requires role sndevops.admin. Connect tools, create applications, automate change requests, and enable change control in orchestration pipelines.
      • Tool Owner: Requires role sndevops.toolowner. Similar responsibilities as admin, but dependent on admin for application creation.
      • App Owner: Requires role sndevops.appowner. Collaborates with admin/tool owner to connect tools and create applications.
    • Workspace Widgets:
      • Tools Widget: Displays the status of connected tools, those needing attention, and groups them by capabilities and types.
      • Applications Widget: Shows applications with associated pipelines, work item statistics, and allows app creation.
      • Automated Change Requests Widget: Provides insights into change requests created, pending approvals, and pipelines with enabled change control.

    Key Outcomes

    Successful onboarding leads to automated change requests, streamlined DevOps processes, and effective monitoring of tools and applications. Users can expect enhanced visibility into their tools and applications, increased efficiency in handling change requests, and improved collaboration among team members.

    After installing DevOps Change Velocity, you can integrate with your DevOps toolchain and automate change requests directly from the DevOps Change Workspace.

    You can onboard as a DevOps admin, a tool owner, or an app owner.

    Onboard as DevOps admin

    Role required: sn_devops.admin.

    1. From the Home page, from the Get started with DevOps Change Velocity guide, select Connect a tool.

      Onboarding page for DevOps admins.

      Note:
      To automate change requests for pipelines, connect your orchestration tool.
    2. Using the connect playbook activity, connect to your DevOps tools.

      For more information about connecting to a tool, see Integrating DevOps Change Velocity with third-party tools.

    3. Select Create an application to create an application and associate objects to it.

      For more information about creating an application, see Create an application - Workspace.

      Create an application.

    4. To automate change requests for pipelines, connect your orchestration tool and associate the pipelines with your application.

      For more information on associating pipelines, see Associate tool objects to applications - Workspace.

    5. Select Automate change to create an automated change request.

      For more information about creating automated change requests, see Automate DevOps change request creation.

      Automate change requests.

    6. Modify your orchestration pipeline to enable change control.

      You can run the pipeline to verify that change requests are automatically created.

      Waiting for change request creation.

    The getting started guide will be marked as complete when the first automated change request is created by the orchestration pipeline.Completed getting started guide for tool owner.

    Onboard as a tool owner

    Role required: sn_devops.tool_owner.

    1. From the Home page, from the Get started with DevOps Change Velocity guide, select Connect a tool.

      Connect a tool.

      Note:
      To automate change requests for pipelines, connect your orchestration tool.
    2. Using the connect playbook activity, connect to your DevOps tools.

      For more information about connecting to a tool, see Integrating DevOps Change Velocity with third-party tools.

    3. If an application hasn't been created, ask your DevOps admin or app owner to create an application and associate objects to it.

      For more information about creating an application, see Create an application - Workspace.

      Ask app owner to connect an application.

    4. To automate change requests for pipelines, connect your orchestration tool and associate the pipelines with your application.

      For more information on associating pipelines, see Associate tool objects to applications - Workspace.

    5. Select Automate change to create an automated change request.

      For more information about creating automated change requests, see Automate DevOps change request creation.

      Automate change requests.

    6. Modify your orchestration pipeline to enable change control.

      You can run the pipeline to verify that change requests are automatically created.

    The getting started guide will be marked as complete when the first automated change request is created by the orchestration pipeline.Completed getting started guide for tool owner.

    Onboard as an app owner

    Role required: sn_devops.app_owner.

    1. Ask your DevOps admin or tool owner to connect to your DevOps tools.

      Getting started guide for app owners.

      Note:
      To automate change requests for pipelines, connect your orchestration tool.
    2. Select Create an application to create an application and associate objects to it.

      For more information about creating an application, see Create an application - Workspace.

      Create an application.

    3. To automate change requests for pipelines, ask your DevOps admin or tool owner to connect your orchestration tool.
    4. Associate the pipelines for which you want to automate change requests with your application.

      For more information, see Associate tool objects to applications - Workspace.

    5. Select Automate change to create an automated change request.

      For more information about creating automated change requests, see Automate DevOps change request creation.

      Automate change requests.

    6. Modify your orchestration pipeline to enable change control.

      You can run the pipeline to verify that change requests are automatically created.

    The getting started guide will be marked as complete when the first automated change request is created by the orchestration pipeline.Completed getting started guide for app owner.

    Workspace widgets

    Tools widget
    The Tools widget gives an overview of your connected tools, with the following details:
    • Number of tools that are in the connected state. You can select the card to see the list of connected tools.
    • Number of tools that need attention. You can select the card to see the list of unconfigured tools.
    • Number of tools that are in disconnected state. You can select the card to see the list of disconnected tools.
    • Number of tools grouped by their capabilities. You can select a capability to see the list of tools created for that capability.
    • Number of tools grouped by their tool types. You can select an integration type to see the list of tools connections created for that particular tool type.
    • DevOps admins and tool owners can connect to a tool from the widget.

    Tools widget.

    Applications widget
    The Applications widget gives an overview of your applications, with the following details:
    • Number of applications with at least one associated pipeline. You can select the card to see the list of apps with pipelines.
    • Number of without any pipelines. You can select the card to see the list of apps with no pipelines.
    • Number of work items, commits, and pipeline executions from all applications in the last 30 days. You can select the card to see the list of disconnected tools.
    • Number of tools grouped by their capabilities. You can select a capability to see the list of tools created for that capability.
    • Number of tools grouped by their tool types. You can select an integration type to see the list of tools connections created for that particular tool type.
    • DevOps admins and app owners have the option to create an application from the widget.

    Applications widget.

    Automated change requests widget
    The Applications widget gives an overview of your applications, with the following details:
    • Number of change requests created in the last 30 days. You can select the card to see the list of change requests.
    • Number of change requests that are pending approval in the last 30 days.
    • Number of pipelines with change control enabled, but hasn't automatically created a change request.
    • Number of tools grouped by their capabilities. You can select a capability to see the list of tools created for that capability.
    • Number of tools grouped by their tool types. You can select an integration type to see the list of tools connections created for that particular tool type.

    Automated change requests widget.