Release Update 02/28/2025

SDLC

Introducing Gerrit to GitHub Migration

In addition to the current SCM migration workflows, users now have the capability to transfer data from Gerrit to GitHub. This feature allows for a smooth migration of repositories while ensuring that critical components such as files, groups, and organizational structures are retained.

Furthermore, the migration process encompasses the transfer of pull requests, fostering continuity in collaborative efforts and code review practices. A comprehensive migration of commit history is also supported, guaranteeing a complete and auditable record of all project modifications.

Upon initiating the migration, Opsera generates detailed reports that furnish users with comprehensive insights into the migration's progress and outcomes. This meticulous approach ensures that the transition from Gerrit to GitHub is executed with precision and accountability, facilitating a smooth and efficient code migration experience.

Enhance Your Pipeline Workflows with Copacetic and Lineaje Integration to Improve Software Delivery Quality

Opsera has introduced the integration of Copacetic’s automated testing features and Lineaje’s data lineage tracking within Opsera Pipelines. The integration capability ensures that all code changes undergo comprehensive testing, minimizing the risk of negatively impacting data integrity or workflows. By automating both testing and data lineage analysis in the DevOps pipeline, development teams can identify and resolve issues early in the development cycle. Copacetic provides instant feedback on code modifications, while Lineaje offers real-time insights into data lineage, enabling developers to quickly pinpoint and address problems.

This integration promotes better teamwork between development and data teams, ensuring that code changes are not only functionally correct but also compliant with data standards.

• Report Generation for Lineaje Scan Result and Vulnerability Comparison

Opsera generates reports for the Lineaje scan results and vulnerability comparison after the completion of the workflow. Users can access a comprehensive comparison of vulnerabilities detected in an image both prior to and following patching, allowing them to assess the effectiveness of their patching efforts. The report features metrics such as the total number of vulnerabilities resolved, any newly introduced vulnerabilities, and outstanding issues that remain. Furthermore, users have the option to download the PF (Patch Findings) report produced by Lineaje, which summarizes all findings related to the patches that have been applied.

Insights NX

Capability to View Commit ID and Links Specific to a Deployment

A new column labeled “Commit ID” has been added to the Deployment Frequency KPI Table. This column will provide links to GitHub commit IDs for each deployment outlined in the table. This capability allows direct access to relevant GitHub commit details, which will enhance traceability and enable deeper analysis of the deployment process.

Team Level Filter for Codebase Activity

The new team level filter for Codebase Activity in the GitHub Copilot Dashboard provides users with a more granular view of GitHub Copilot’s performance across different teams. With the capability, users can gain a deeper understanding of how GitHub Copilot is being used within their organization.

This feature enables users to:

• Track codebase activity at the team level

• Compare the performance of GitHub Copilot across different teams

• Identify areas where GitHub Copilot can be improved or optimized

New Capabilities for the Change Request KPI

A Filter capability has been introduced to the Change Request KPI table. This allows users to retrieve data based on specific criteria, including project selection, creator, and current status. Furthermore, the capability to export KPI data in both CSV and PDF formats has been added for improved accessibility and reporting.

Additionally, the date filter on the release dashboard has been updated. It will now reflect the planned Start and End Dates of projects instead of relying solely on the creation date of change requests. This helps to provide a more accurate representation of timelines associated with change requests.

Introducing Automated Email Notification for GitHub Copilot Reports

Users can set up to receive email notifications for GitHub Copilot reports. The timely notifications help your team stay informed by sending automated updates on important metrics, such as the Dev Productivity Report and the Copilot Usage Report. You can customize your notifications by choosing specific metrics, date ranges, and organizations, and select how often you want to receive them. You can also add multiple email addresses to ensure that everyone involved is kept in the loop. This capability aims to improve your development workflow and provide valuable insights directly to your inbox.