Release Update 07/27/2024
Salesforce
Opsera extends support to OmniStudio Metadata
The following Omnistudio components can be used in the Pipelines, Tasks and other wizards for Salesforce workflows created in Opsera
AssessmentQuestion
AssessmentQuestionSet
OmniInteractionConfig
OmniInteractionAccessConfig
Capability to Skip Test Executions for Configuration Components
Users can save time during deployment processes, with the capability to skip any test executions in the Validate and Deploy Steps in their pipeline workflow.
When a package is being validated or deployed, if the package.xml does not include any Apex classes, Opsera will automatically skip the execution of Apex tests. This functionality operates independently of any unit test settings configured in the pipeline. Therefore, regardless of whether unit tests are set up at a specific level, if there are no Apex classes present in the package, Apex test execution will be bypassed.
Change in Default Build Type in Salesforce Configurator Tool Registry and Workflows
Default Build Type Update: Previously, when registering a new Salesforce Configurator tool in the Tool Registry Wizard, the default build type was set to ‘ANT Metadata Format’. With this release, we have updated the default build type to ‘Salesforce DX (Source Format)’. Users have the flexibility to switch back to ‘ANT Metadata Format’ if required.
Default Build Type Configuration: In scenarios where Salesforce Repo is enabled within the Git to Git Merge Sync Task, the default build type was previously left blank. With this release, the default build type is set as ‘Salesforce DX (Source Format)’. Users will still retain the option to change this setting to ‘ANT Metadata Format’.
SDLC
Hummingbird AI generated pull requests for Bamboo to GHA Migration workflows
A capability has been introduced using Hummingbird AI technology to facilitate pipeline migration from Bamboo to GitHub Actions (GHA). Upon the successful completion of a migration, an AI-generated pull request will be automatically created. Please note that only organizations with Hummingbird AI entitlement will have access to these AI-generated pull requests.
Upon successful completion of a migration, users will observe the generation of pull requests by both GitHub and Opsera platforms.
New Capabilities in SVN to GitHub Migration Mapping
Previously, during the Task configuration, only the standard SVN folder names were mapped directly to Git branches, tags, and the default branch. With this release, we have implemented a more flexible mapping system that recognizes multiple custom-named folders within the SVN repository. This allows users to define specific folder names during the configuration step.
Users can specify multiple folders that should be treated as branches or tags, ensuring that all relevant data is captured and migrated accurately.
Additional Capabilities
Users can leverage the Docker CLI within their pipeline steps to push Docker images directly to GCR. This integration simplifies the workflow by allowing developers to manage their container images efficiently without leaving the pipeline environment.
Users can create a dedicated Jenkins-based push step using Jenkins as their CI/CD tool to automate the process of pushing Docker images that are built during the Jenkins workflow execution. The new Jenkins step integrates seamlessly with existing Docker build steps, ensuring that once an image is built, it can be pushed to GCR without additional manual intervention.
The field label in GitHub Tool registration previously known as ‘Personal Access Token’ has been updated to ‘Personal/User Access Token’
Last updated