Release Update 04/2024

SDLC & DevSecOps

Rewire Source Account, Repository and Branch for Opsera Pipelines post SCM Migration

After a successful SCM migration process, the GitLab /GitHub /Bitbucket values can be updated to GitHub values in Opsera Pipelines using the SCM Pipeline Source Migration API or by configuring rewire toggle in SCM task settings. With the help of this functionality, repositories and branches can be rewired by deleting the current source SCM values (GitLab/GitHub/Bitbucket) and substituting new GitHub values.

If pipelines are not rewired after the migration, the new GitHub settings may conflict with existing git configurations, resulting in errors or odd behavior when the pipeline executes. To maintain smooth and correct operations after an SCM migration, pipelines must be rewired to reflect the new GitHub settings. For more info, read here.

Opsera Pipelines Integrated with Nexus IQ for Open Source Governance

The Nexus IQ integration for Opsera Pipelines improves code security by detecting and alerting customers to vulnerabilities in their code. This integration will help identify security flaws in open source dependencies, containers, and infrastructure as code by scanning code repositories. This proactive strategy enables developers to fix possible problems before they become serious security vulnerabilities. For more info, read here.

Insight

Jira Sprint Duration Analysis with Opsera’s KPI

Teams can track and evaluate sprint durations by using the Jira Sprint Velocity KPI to obtain information on the start and completion dates of Jira sprints. By analyzing Jira sprint start and finish dates, teams may track progress, identify trends in sprint durations, and improve future sprint planning.

Understanding typical sprint durations and timing helps teams to improve estimation accuracy, balance workloads, and improve overall sprint performance. For more info, read here.

Salesforce

Support to view the package XML in the Git to Git Task execution report

The package XML file is displayed in the Git to Git Merge Sync Task execution reports, listing the metadata elements that were a part of the commit.

Using Package XML with the component chart, users can track and understand which components are being modified or merged to the branch . The XML file usually contains entries for many types of metadata, such as objects, fields, classes, profiles, and so on. To learn more, read here.