What Is Release Management In Salesforce DevOps? - PowerPoint PPT Presentation

About This Presentation
Title:

What Is Release Management In Salesforce DevOps?

Description:

Before Salesforce DevOps came into existence, developers used to (and still) build SF apps using the waterfall method. In this method, the developers are offered various kinds of Sandboxes where they can develop Salesforce apps or upgrade existing ones. – PowerPoint PPT presentation

Number of Views:71
Slides: 6
Provided by: braydendiegoven

less

Transcript and Presenter's Notes

Title: What Is Release Management In Salesforce DevOps?


1

Click to d text
  • What is Release Management in Salesforce DevOps?

2
Traditional Salesforce Release Management
  • Before Salesforce DevOps came into existence,
    developers used to (and still) build SF apps
    using the waterfall method. In this method, the
    developers are offered various kinds of Sandboxes
    where they can develop Salesforce apps or upgrade
    existing ones. The release management looks like
    this
  • Developer develops an SF app in the Sandbox.
  • The code then goes to the Integration org where
    it is tested for bugs and inconsistencies.
  • If everything looks good, it goes next to the UAT
    org where its performance is checked against the
    requirement.
  • Finally, the app goes to the staging environment
    and then to Production.

3
How Release Management in Salesforce DevOps Works
  • SF and DevOps is a match made in heaven. Just
    like in other programming-heavy industries,
    DevOps has brought the Development and
    Operations, teams, closer with Salesforce
    DevOps, the same thing is happening in
    organizations that depend on Salesforce.
  • Unlike the traditional model, typical release
    management in DevOps entails
  • Version control
  • Ci/CD pipeline
  • 26 releases per year as opposed to just 4
    releases in the traditional model.

4
The release management Works like this
  • Developers transfer the code from the Sandbox to
    a version control system.
  • The version control system is integrated with the
    CI/CD platform.
  • The units of code are tested by the Integration
    org leveraging the CI server. These tests happen
    during the development process. Every time a
    cohesive unit of code is sent to the repository,
    it is automatically tested.
  • Once the test passes, the code is promoted to the
    Integration org and then to UAT org. After
    further tests, it is deployed to the Staging
    environment and then to Production. This
    continuous deployment is also an automated
    process. 
  • This entire release management in SF happens
    automatically.

5
Contact us or Request a demo
https//www.autorabit.com/request-a-demo/
info_at_autorabit.com 1 925 500 1004 548 Market
Street PMB 98272San Francisco CA94104-5401 www.a
utorabit.com 
Click to add text
Click to add text
Write a Comment
User Comments (0)
About PowerShow.com