Vancouver |
- DevOps change models
- Use change models in DevOps Change Velocity that enables better flexibility in defining change models or processes to reflect modern development practices.
- Secure token authentication for integration user
- Configure Azure DevOps, Jenkins, and GitHub Actions using token-based authentication for the integration user for better security.
- ServiceNow DevOps change request state in Azure DevOps pipeline logs
- View the change request state and the corresponding policy conditions in the Azure DevOps (ADO) pipeline console logs whenever the state of a change request is updated without having to navigate to ServiceNow®
DevOps Change Velocity.
- Get and update change request details
- Retrieve and update change request details associated with an Azure DevOps pipeline and the GitHub Actions workflow by using the ServiceNow® DevOps extensions available in the Azure DevOps and GitHub Actions marketplace.
- Configure webhooks manually
- As a tool owner or DevOps admin, access the token and sys_id for webhooks by configuring webhooks manually in your third-party tool rather than configuring them automatically from ServiceNow®
DevOps Change Velocity.
- GitHub Actions deployment gates
- Enforce quality gates on every deployment environment in GitHub Actions and retrieve the change details from within the Deployment Protection Rule console logs of GitHub Actions.
- Simplified setup
- Spend less time in the initial setup of ServiceNow®
DevOps Change Velocity thanks to the removal of the CreateDevOpsTool connection setup activity.
- Validate ServiceNow DevOps extension in Azure DevOps
- Validate the installation of ServiceNow
DevOps extension in Azure DevOps with a playbook activity.
- Configure webhooks automatically in Rally
- Configure webhooks automatically as part of the playbook while connecting to the Rally tool.
- Assign services to the pipeline steps
- While associating pipelines with an application, for each selected pipeline, all steps or stages are imported from the last successful execution.
- Update change model in pipeline
- Update the change model in your existing pipeline steps using the DevOps Pipeline Migration to Change Models catalog item.
- Manage ADO pull requests
- Manage Azure DevOps (ADO) pipeline's pull requests for ADO coding source from ServiceNow DevOps. You can enable the change approval process on your pull request to control pull request merge approvals from ServiceNow DevOps and monitor pull request details associated with the change request.
- New test types supported for ADO
- Automatically publish ADO test results of test tools reports like NUnit, pytest, jest, JUnit, and XUnit without any custom API calls.
- GitHub OAuth JWT setup through playbook
- Configure the GitHub tool using OAuth JSON Web Token (JWT) credentials through the tool onboarding playbook.
- GitHub Organization support
- Configure and discover GitHub repositories under an organization.
- Automatic updation of close code based on pipeline execution status
- Change created from a pipeline is now automatically closed and updated with the closure notes, actual start and end time, based on the overall pipeline completion status.
- Guided change automation experience
- Use better in-product guidance on the various ways to leverage DevOps changes and easily adopt the changes without complete disruption of your change process.
- Renamed DevOps flows
- The DevOps Model Change Approval and DevOps Default Change Approval flows have been renamed to DevOps Change Request Manual Approval and DevOps Change Request Advanced Automation Approval flows respectively.
- Getting started guide
- Use the Getting started guide from the DevOps Workspace Homepage to get started with DevOps Change Velocity after installation.
- Create applications using playbook
- Use the App playbook to create DevOps applications, associate plans, repositories, and pipelines, and import historical data.
- Configure Jenkins automatically
- Configure the Jenkins tool automatically directly from within DevOps Change Velocity.
- 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.
- 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.
- 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.
|
Washington DC |
- 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.
|
Xanadu |
- Reflow for configurable workspace
- DevOps Change Configurable workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality. For more information, see
the Accessibility information section that follows.
- DevOps data in change request
- View, add, and edit DevOps data in a manually created change request in Service Operations Workspace for a unified change request experience in both DevOps Change Workspace and Service Operations Workspace.
- 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.
- Enhanced manual DevOps change creation experience
- Add work items data in a manually created DevOps change request in Service Operations Workspace for ITSM.
- 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.
- Additional scans for DevOps Health Scan Content pack
- Additional set of proactive checks focused on problems that tend to occur before or after an upgrade along with identifying configuration issues like plugin and version incompatibilities, or pipelines that chronically fail,
have been added.
- Import pull-request records for Bitbucket Server or Bitbucket Data Center
- Import pull-request records for Bitbucket Server or Data Center for improved insights and efficiency.
- Change request creation with errors in DevOps data retrieval for Harness pipelines
- Enable change request creation even if there is an error in retrieving the DevOps data for a Harness pipeline.
- Branch name filter
- Search for build numbers by the branch name while associating DevOps data to a change request in the Service Operations Workspace (SOW) or Classic UI.
- Test summary name in GitHub Actions
- The servicenow-devops-test-report custom action in GitHub now includes an optional test-summary-name parameter to specify the test summary results name.
- Token based authentication for Rally
- Configure webhooks for Rally using token based authentication instead of using the integration username and password.
- Renamed variables for Docker
- The environmental variables in the Generic Docker actions for DevOps Change Velocity have been renamed by removing the CI prefix for better clarity.
- Security scan results
- Security scan results on the change record associated to a pipeline execution with a linked package are now displayed in the Security Summaries tab.
- Source of commits in SOW
- View the source of commits like pipeline execution, branch, repository, and so on for a change request in the DevOps data section of the Service Operations Workspace.
- Track file changes
- The Track file changes option is now disabled by default when a repository is configured to prevent any potential security risks.
- Close code value for a change request
- Two new properties have been added in DevOps Change Velocity, so that you can specify a close code value for a change request based on the change request completion state when the autoCloseChange parameter is enabled.
- Support for MID Server cluster
- Improve load balancing and failover protection by selecting a MID Server cluster when connecting to a tool instance associated with a MID Server cluster. This configuration enables multiple MID Servers with relevant capabilities to be grouped.
- Improved UX for DevOps Change health scans
- Run health scans and analyze findings efficiently in the DevOps Change workspace with an intuitive and user-friendly interface.
- Pipeline association for GitHub Actions
- When onboarding GitHub Actions pipelines through the App onboarding catalog or the onboarding APIs, now only the selected pipelines are associated with the DevOps app. If no pipeline is selected, all pipelines within the specified repository are associated.
- Tool connection check status
- If a tool is marked as Disconnected because of a system-generated failure during an unsuccessful connection check, any subsequent successful check automatically updates the connection status to Connected. If you manually
disconnect the tool, the tool status remains Disconnected even if there’s a subsequent successful connection check.
- New roles for vulnerability integration
-
- The sn_vul.app_sec_manager role is added to the DevOps Tool Owner [sn_devops.tool_owner] role when the DevOps Vulnerability Integrations plugin (sn_devops_vul_ints) is installed.
- The sn_vul_veracode.configure_integration role is added to the DevOps Tool Owner [sn_devops.tool_owner] role when the Vulnerability Response Integration with Veracode plugin (sn_vul_veracode) is installed.
|