DevOps Change Velocity release notes
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 DevOps Change Velocity Release Notes
The ServiceNow® DevOps Change Velocity application has been updated in the Washington DC release, enhancing visibility into DevOps data, automating change processes, and providing insights to measure DevOps performance. This release introduces significant integrations and features aimed at improving your DevOps workflow.
Show less
Key Features
- GitHub Issues Integration: Link GitHub issues with code commits for better planning.
- Custom Actions for GitLab: Collect data related to change requests and automate processes using Docker images.
- User-Created Orchestration Tool Support: Integrate with non-base orchestration tools to manage webhooks and historical data.
- Jira Cloud Integration: Track Jira issues directly within DevOps Change Velocity.
- OAuth 2.0 Authentication: Securely connect Azure DevOps and Jira Cloud using OAuth 2.0.
- Enhanced Automated Change Creation: Improved procedures to avoid issues during automated change requests.
- Multiple ServiceNow DevOps Configurations: Support for configuring multiple connections in a single Jenkins instance.
- Simplified Change Model: New model streamlining the change process without the Assess state.
- Customizable Lists: Create personalized lists within the application for better management.
Key Outcomes
With the Washington DC release, ServiceNow customers can expect improved efficiency in change management processes, enhanced tracking of DevOps workflows, and better integration with existing tools. This update allows for a more streamlined, automated, and secure environment, facilitating smoother transitions and approvals within DevOps practices.
The ServiceNow® DevOps Change Velocity application improves visibility into your DevOps data in a single system, automates and accelerates change processes, and helps you gain insights to measure the performance of your DevOps environment. DevOps Change Velocity was enhanced and updated in the Washington DC release.
DevOps Change Velocity highlights for the Washington DC release
- Discover GitHub issues in GitHub repositories as part of the planning capability.
- Collect data related to change request creation, Sonar scan, artifact registration, and package registration in your GitLab pipeline.
- Retrieve data associated with a change request using the DevOpsChangeRelationshipHelper script.
See DevOps Change Velocity for more information.
Important:
DevOps Change Velocity is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes.
New in the Washington DC release
- GitHub Issues integration
- Discover GitHub issues in GitHub repositories as part of the planning capability to link the GitHub issues with GitHub code commits.
- Implement custom actions for pipelines using generic Docker container image
- Collect data related to change request creation, Sonar scan, artifact registration, and package registration in your GitLab pipeline using the custom actions for GitLab.
- User-created orchestration tool integration support
- Integrate DevOps Change Velocity with any orchestration tool that is not supported in the base system to discover the orchestration tool, configure webhooks, import historical data, receive live data, and enable change control on your pipelines.
- GitLab pull request for change approval
- Track GitLab merge request (pull request) pipeline executions in DevOps Change Velocity, link pull request and orchestration pipelines and to enable change approval tracking.
- Jira Cloud integration
- Integrate DevOps Change Velocity with Jira Cloud and track Jira Issues for the configured projects.
- JFrog Artifactory for GitHub, GitLab, and Azure DevOps
- Import the artifact data published to JFrog Artifactory for the corresponding pipeline executions for GitHub Actions, GitLab, and Azure DevOps.
- OAuth 2.0 authentication for Azure DevOps (ADO)
- Use OAuth 2.0 authentication to connect your Azure DevOps tool with DevOps Change Velocity ensuring a more secure authentication method.
- OAuth 2.0 authentication for Jira Cloud
- Use OAuth 2.0 authentication to connect your Jira Cloud tool with DevOps Change Velocity ensuring a more secure authentication method.
UI changes
- Change module
- A Change module has been added to the application navigator that contains change control and pipeline change request lists.
- List module
- A List module has been added to the application navigator that contains artifact, package, and pending package lists.
Changed in this release
- Enhanced automated change creation
- Avoid issues that might occur in the automated change request creation guided procedure because of the tool connection state.
- New state transition flows for DevOps change model
- Move and track changes through added transition flows for the Change - DevOps - New and Change - DevOps - Schedule states in the DevOps change model.
- Error handling for DevOps flows
- View errors corresponding to a change request in the work notes of a change request and console logs of the pipeline tool when a business rule or data policy causes an issue while updating a change in the DevOps Change Request Manual Approval, DevOps Change Request Minimal Automation Approval, or DevOps Change Request Advanced Automation Approval flows.
- DevOpsChangeRelationshipHelper script to retrieve change data
- Retrieve data associated with a change request based on the specified relation type using the DevOpsChangeRelationshipHelper script include.
- New property to specify retry limit
- Specify the maximum number of times the discover action will be automatically retried after it reaches the rate limit using the Maximum limit for the number of times the discover action that exceeds the rate limit will be retried property.
- Import request restart
- Restart an import request from the Import Request record that couldn’t be completed due to an error.
- Automatically associate repositories
- Repositories are automatically associated to applications when a corresponding pipeline identifies commits of repositories that are not yet associated.
- Unit test type support for GitHub
- Automatically publish unit test results of types NUnit, pytest, jest, JUnit, and XUnit from GitHub Actions workflows without any custom Application Programming Interface (API) calls.
- Change request creation with errors in DevOps data retrieval
- Enable change request creation even if there is an error in retrieving the DevOps data in a pipeline.
- Multiple ServiceNow DevOps configurations in the same Jenkins instance
- Configure multiple ServiceNow DevOps connections in one Jenkins server.
- Custom actions for GitLab using Docker
- Retrieve and update change request details associated with a GitLab pipeline and publish unit test results. Automatically update close code based on the overall pipeline execution status for simple GitLab pipelines.
- Manual retry of downstream events
- If an error occurs for an event, and there are subsequent downstream events associated with it, then you must manually retry each downstream event by selecting the Retry button. Automatically retrying of downstream events is not supported anymore.
- Enhancements to DevOps Model change
-
- In-product guidance enables you to leverage DevOps models and easily create DevOps changes without disruption of your change process.
- To make the Change - DevOps – Implement flow of the DevOps model more suitable for DevOps changes, change tasks are no longer automatically created.
- The new Change – DevOps – Update execution state flow in the DevOps model means you no longer have to activate the DevOps Change Request Manual Approval flow to send a callback to the third-party orchestration tool.
- Fast-track your change process by using a new DevOps Simplified change model, which doesn’t contain the Assess state. Change approval for this model is based on the DevOps Simplified Model Change policy.
- Branch details for artifacts and packages
- Branch details from pipeline executions are now available for artifacts and packages for better tracking.
- Create lists
- Option to create customized lists added to the Changes, Tools, and Administration modules in the DevOps Change Workspace.
- Jira Server connection using API key
- Connect to your Jira Server using API key authentication rather than basic authentication.
- GitHub Actions reruns
- Re-running failed GitHub jobs will now use the existing change request created for the failed jobs instead of creating new change requests.
- Generalized Docker Container solution to support any orchestration tool
- Use the generalized and extensible Docker Container solution to integrate any orchestration tool with DevOps Change Velocity for invoking pipeline actions like change request creation and collecting relevant DevOps data without having to rely on tool specific plugins or extensions.
- Simplified onboarding of planning tools that are not supported in the base system
- Integrate planning tools that are not supported in the base system by leveraging transformer rules. GitLab Issues is now available as one of the planning tools and is built leveraging this new approach so you can discover plans, import work items, and configure webhooks for work items (issues) in GitLab.
- Default BitBucket branch property
- Specify the default Bitbucket branch name that must be used to create an import request in the sn_devops.bitbucket_default_branch property.
Activation information
Install DevOps Change Velocity by requesting it from the ServiceNow Store. Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.