Release Update 02/22/2024

Salesforce

Introducing a Task to Compare Salesforce Profiles and Deploy

Salesforce users now have the ability to compare profile permissions between two Salesforce organizations and deploy the results into the destination organization, with a single dedicated task. Users can also assess and move changes to profile permissions within a single organization using this task.

The task execution details allow users to gain a better understanding of the deployment through reports and console logs, which include information such as the component name, file name, performed action, and path. For more info, read here.

Salesforce Code Analyser version Upgrade to 3.21.0

The sf scanner plugin has been upgraded to 3.21.0. This upgrade includes the addition/deprecation of Salesforce rulesets.

Rules Added

• AvoidMultipleMassSchemaLookups

• UseWithSharingOnDatabaseOperation

• PerformNullCheckOnSoqlVariables

• RemoveUnusedMethod

Rules Deprecated

• no-extra-semi

• no-mixed-spaces-and-tabs

• no-mixed-spaces-and-tabs

• UnusedMethodRule

SDLC & DevSecOps

Capability to include the email ID of the user executing the Jenkins CLI step.

The user who runs Opsera Pipeline via the Jenkins command line interface to access a script or shell environment is now recorded in the console log. The user's email address is displayed in the console log for the corresponding Pipeline run. The console log previously only displayed the pipeline ID, step ID, and run count.

Capability to add Artifcatory for Helm Repositories in Argo Tool

Users can access the Helm Chart Repository in Artifactory in Opsera Pipelines. When the Argo tool's repository is created, users are given the capability to build an artifact repository for their Helm Charts. This was previously limited to the Git Repository type. For more info, read here.

Capability to Generate and Download Reports for Command Line Pipelines

Users can generate reports while executing Pipeline steps for the Command Line Tool. Previously, users would download the report file from the jenkins instance to analyze results.

The downloaded reports can contain log files, test results or step run artifacts. The goal is to view and analyze the step details, after pipeline execution.

Users can specify the report's name and output file path to set up this configuration at the step level in Opsera Pipelines. Once the pipeline has run, users can download it from the Pipeline Logs in Opsera. In addition, the report will be stored in the specified file path. For more info, read here.

Additional Field Validations for SCM Migration Task

The following validations have been added to the task creation form's fields:

• During the Repository Mapping, a case-insensitive duplicate check will be carried out on the Source and Target repositories.

• Users can edit to change the Target repository name without overriding the current target repository when they run into an override repository error. Previously, users could only override the repository.

Capability to Add and Reuse Output Parameters mappings across the Build Pipeline Steps

When configuring the build steps in Pipelines, users can create Output parameters by mapping the parameters with the respective keys. In addition, you can also reuse the output parameters in the pipeline's subsequent build steps. This updates the Output keys values to the most recent parameters

For this, users need to enable the Use Build Step Resource and select the respective build name whose output parameters need to be added/updated. Currently we support this for Docker and Maven build steps. For more info, read here.

Insights

Collect and Evaluate Jmeter Results - Introducing new KPI for JMeter Pipelines

Users can view the test results for various Jmeter pipelines by adding the Jmeter Results KPI to their Opsera dashboards. Analyze the Pipeline's results by understanding its success and failure counts. The actionable insights report, which displays details such as response code/message, thread name, URL, and more, allows you to interpret results more deeply. For more info, read here.