Introducing a Task to Migrate Salesforce Custom Settings Data (Beta) Opsera now has a new task type that makes it simple to migrate custom Setting data in Salesforce. This provides two options:
Provide visibility across the company with Jira integration that automatically retrieves data from the Opsera Task and updates the relevant JIRA with commit information. Track and associate Opsera’s Salesforce to Git Merge Sync task and Git to Git Merge Sync Task into Jira Tickets.
Enable subscription for specific tasks that are created by users in the organization. All subscribed tasks can be managed under a single screen.
A brand-new navigation bar is introduced in Opsera to enable users to quickly navigate to Home, Workspace, Unified Insights and Git Custodian features. To learn more, read here.
You can view report details of all user accounts and their status (active or not), along with information about their organization domain and customer ID.
When running your Salesforce Tasks/Pipelines, choose the version of the Metadata API that Salesforce will use to retrieve or deploy your components. This is supported for Salesforce Pipelines, and Salesforce tasks for Org Sync, Bulk Migration and Salesforce to Git Merge Sync Task.
New filter options are introduced as you look up a specific Salesforce component. This enables quick and better retrieval of specific data. In addition, the UI is tweaked for better user experience. To learn more, read here.
Create build steps for iOS Apps using Xcode job type in Jenkins Pipelines. To learn more, read here.
Previously, branch details were validated as the task was being executed when new branches were being created or when providing a target branch for Salesforce Tasks. This update now validates the branch prior to component selection in the Wizard.
The KPI measures the performance of DORA metrics and has an improved User Interface indicating the current maturity, along with previous maturity and their trends over time. Each Organization opens a maturity timeline and then displays a drill down maturity timelines for groups within it and so on. To learn more, read here.
By integrating and setting up pipelines with the Oracle Fusion Instance Tool, users can now move BI reports from one Oracle Fusion Instance to another Fusion Instance. Moreover, it is supported to export reports via Pipeline from Artifactory to the desired instance. To learn more, read here.
View the access token usage report after a user successfully authenticated and authorized access, along with the Token ID and Target API. In addition, view the Token ID, Scope, as well as usage date and time information from the activity logs for a particular user. To learn more, read here.
View the vulnerability report in detail for pipelines used for security scans using Black Duck, Anchore, Snyk, Aquasec, Coverity, and Sonar apps. To learn more, read here.
The approver will have direct access to the Pull Request URL, together with the Pipeline ID, User name, and other information, to see and complete the approval.
In addition to fetching artifacts from the central maven repository, users can now download artifacts from their private JFrog artifactory during Jenkins build
When creating a pipeline build step for Gradle using Jenkins, users can now select multiple Gradle build versions. To learn more, read here.
Users can now configure their GitLab, GitHub or Bitbucket to trigger a webhook for the Pipeline when a Pull Request event occurs. To learn more, read here.
Get a real time high-level analysis of the health of your code throughout the DevOps pipeline. Using this visibility, manage your Salesforce code and develop functionalities that meet end user expectations. For more info, read here.
KPI for Lead Time for Changes and Deployment Frequency can be created for Pipelines deployed using monorepo. For more info, read here.
Users with a Security Manager and Auditor role can access the Platform and Insights Settings under Settings option in the Opsera Portal. This allows security teams to view analytics settings, portal users, user groups, and site roles. To learn more about role permissions, read here.
Integrate ServiceNow to your Opsera Pipelines, to approve the deployment from the ServiceNow Change requests, prior to deploying the code in the target environment. For more info, see ServiceNow Integration.
Receive alerts when all or certain actions are performed for specific Pipeline, Tasks or Tools. You can, for instance, configure triggers for your important pipelines so that you are informed whenever the configuration of the pipeline changes. For more info, read here.
Merge Profile components during Salesforce to Git Merge, in addition to Salesforce components to a target branch. For more info, read here.
When users click on the visualization charts for Deployment Frequency and GitLab Lead Time for Changes KPI, a drill-down report is available. This granular level of data helps to identify how the data was generated.
Users can now edit and update Vulnerability Severity Rating (Low, Medium, High and Critical) for one or multiple commits. In addition, support to create Jira Tickets for all commits at once is introduced. For more info, see GitCustodian Insights
In the event that the Azure Webapp deployment fails, redeploy the most recent version that has been successfully delivered. While configuring the Pipeline step, you can select the version to which you want to roll back. Read more here.
(i) Pagination is introduced to improve quick navigation and reduce scrolling. (ii) Support for keyword searches in the search option for Argo applications, projects, or repositories.
Developer 360 metrics makes it easier to view real-time commits, lines of code, commit review scores, and other information on user activity. View data that is collated for each user’s activity for a GitLab project, tag and a date range. Read more here.
GitLab Deployment Frequency and Jira MTTR KPI now offer the display of Median Value to measure the metric's central tendency. This performance indicator makes it possible to locate the value that lies exactly halfway between the top and bottom data. Read more about Jira MTTR and Gitlab Deployment Frequency KPI.
You can look at reports for a specific Opsera tag combination. The report that is generated for the desired tags is also available for download. Read more here.
Get an overview of the security issues based on the severity (Critical, High, Medium, Low and Negligible). Issues can be identified and resolved more quickly with exportable detailed reports. Read more here.
For the Github Actions events that are triggered by webhook, users can receive insights. The metrics are downloadable and provide detailed information on distinct workflows that succeeded and failed at the job and pipeline step levels. Read more here.
Users can alter Source and target branches, or create a new branch at the time of Salesforce task execution. This eliminates the need to change the branches at step settings.
With support for Helm Integration, customers can deploy the image in Kubernetes using helm in Azure and AWS cluster. The deploy step will accept requests as part of orchestration and deliver responses, status updates, and console logs. Read more here
Developers can manage changes to the database, including creating, testing, and rolling back changes, easier using the Liquibase extension for connecting to Redshift and SQL Plus databases. Read more here
For Unit Test (Auto Include) deploy and verify phases, during pipeline execution, and when reading Pipeline logs, relevant error messages are provided.
For the route v2/actions/pipeline/run, JSON support is now available in addition to the existing YAML support. Regardless of the object type, ApiRequestHelper returns the same structured reqBody when the item is identified as YAML or JSON.
Downloadable Git Custodian KPI Report: Git Custodian KPI results can be exported and downloaded as a Report Git Custodian KPI Report Download
Advanced Slack notifications
We added event based pipeline notification for slack on top of alerts & approvals we added in Dec
Opsera bot on Jira marketplace
Opsera bot available in Jira marketplace for place for notifications, alerts and approval of the pipeline.
Using Opsera Jira BOT application, seamlessly manage the CI/CD pipeline activities such as approvals, vulnerability management, testing issues, alerts and execution failures.
Role based access
Role based access for Pipeline and Tool registry
Analytics improvements - Marketplace KPI’s and new features
Tag based reporting for Pipelines
Push to Artifact enhancements
Enhancement on Push to Artifact step to push changes to existing branch / orphan branch / new branch
Deployment features - Zip & Support automatic installation
Enhancements to SFDC test and deploy features
Opsera bot in Slack marketplace
Opsera bot available in Slack Marketplace for place for notifications, alerts and approval of the pipeline.
Including New Test Classes as part of selective test class execution for Salesforce pipelines
We are extending the support to Kubernetes and customers will get a dedicated Kubernetes cluster with enhanced security features (AWS Transit gateway and VPC attachments).
Tool Chain Automation
We have enabled more tools in the platform as part of tool chain automation and those tools are:
New Declarative Pipeline Features
Opsera users will now be able to integrate with the above-mentioned tools without having to write any custom or glue code to construct the pipelines.
We are also introducing additional features to SFDC CI/CD pipelines (Managed objects, profile management, filters and search option, Org to Org movement etc).
New Features being added to Opsera Analytics
New Features being added to Opsera pipeline:
Opsera Pipeline v1.0 will allow existing and new users to choose a release pipeline template by going to Pipeline Beta link. Users can wire up with existing Jenkins at your end or spin up a new Jenkins from our service catalog (Platform) and connect various tools like (Jenkins, Sonarqube, Junit, Jmeter, Selenium, twistlock, S3 bucket for binary upload and AWS code deploy)Note: These changes will not have any data loss or access issue to your existing Kibana URL you received while onboarding.
Features being added to Pipelines:
We have enhanced the Opsera UI with new features under “Dashboard” and “Analytics”.
With this release, you will no longer have to go to your Kibana URL for your dashboard and analytics.
Note: These changes will not have any data loss or access issue to your existing Kibana URL you received while onboarding.
Features being added to analytics in this release:
We're launching an enhanced Opsera UI! During this migration your data and infrastructure set up will remain intact and there won’t be any changes to the URL’s.