Release Update 08/22/2024

SDLC

New Pipeline Migration Capabilities

Migrate Pipeline Workflows from Azure DevOps to GitHub Actions

Developers have the ability to configure tasks to seamlessly transfer Pipeline workflows from the Azure DevOps to GitHub Actions. Opsera also facilitates the conversion of various properties and environment variables during this migration process. This ensures that all necessary configurations are accurately transferred, minimizing disruptions in your CI/CD pipeline.

Throughout the migration process, Opsera acts as a centralized platform for management and monitoring. Developers can track migration progress, monitor statuses, and address any issues that may arise during the migration.

Migrate Pipeline Workflows from GitLab to GitHub Actions

The GitLab to GitHub Actions migration task, automates the conversion of your existing GitLab CI/CD configurations into GitHub Action workflows.

During the migration, Opsera automatically converts.gitlab-ci.yml files to.github/workflows/*.yml files. This migration workflow simplifies the process of moving projects, pipelines, and configurations from GitLab to GitHub Actions, enabling users to leverage the capabilities of GitHub’s CI/CD platform without having to recreate everything from scratch. Real-time logs and reports offer users immediate feedback on any issues that arise throughout the migration process.

Platform

New UI Updates for Home Page

Opsera has made significant updates to the home page view that will elevate your user experience and improve navigation. The “My Account” widget has been completely revamped, with all its data elements now seamlessly integrated into the “Hello <user>” widget.

A new "My Reports" area has been added to give you quick and easy access to all of your user reports. In addition, our widgets for pipelines, tasks, and GitHub Copilot have been updated to match the new home page UI.

Advanced AI Summary View of Pipeline Logs

Opsera has introduced a new syntax for the Hummingbird AI generated Pipeline summary, to elevate the readability and overall user experience when working with Pipeline logs.

The redesigned summary view displays log information in a more structured style, making it easier for users to navigate through crucial data points. Users can see the summary in a structured version, which includes headings, lists, bold and italic text, links, and code blocks.

For successful pipeline executions, users will receive a comprehensive summary alongside critical insights that highlight key performance data. In cases of failed executions, the system will provide not only a summary view but also actionable remediation steps to guide users in troubleshooting issues effectively.

Introducing an API to retrieve user data based on multiple query parameters

Users can get user activity logs via the API endpoint /api/v2/logs/audit/user. This is useful for monitoring and auditing user activity in order to ensure security and compliance inside an organization.

To use this API, users must submit a valid token that matches either the API scope or the Security Logs scope. This token serves as a kind of authentication, ensuring that only users with the appropriate permissions can access the logs.

The API supports the following optional query parameters that allow users to filter the results according to their needs: Date and Time Filters, Pagination, Action, Type and User Identification. By utilizing these parameters effectively, users can tailor their queries to effectively extract relevant information.