sfops
sfpSlackGithub
  • Overview
  • Features
  • Environments
    • Creating an Environment
    • Authenticating to Environments
    • Review Environments
      • Configuring Review Sandboxes
      • Creation and Allocation of Review Sandboxes
  • Project Workflows
    • sfops - Execute Issue Ops
    • sfops - On Pull Request Comments
    • sfops - Close Issues
    • sfops - Execute Every 30 mins
    • sfops - Daily Job Executor
    • sfops - Review Sandbox - Creator
    • sfops - On Push to Branch
    • sfops - Execute Releases to any env
    • sfops - Execute Releases
  • IssueOps
    • Access
      • Request elevated previlege in production
    • Release
      • Release a Domain
      • Hotfix Workflow
  • Changelog
    • November24
    • January25
  • DevCentral
    • Customising Menu
    • Extending using Custom Forms and Issue Ops Actions
  • self managed instances
    • Setup for self managed instances
      • 1. Create repositories
      • 2. Create a GitHub App
      • 3. Setting up sfops repository
      • 4. Trigger the workflows
      • 5. Setting up project repository
      • 6. Fetching upstream changes
        • 6.1 Manual Process for Updating sfops from Upstream
    • Update Instructions
      • Updating to v29.0.0
      • Updating to v30.3.1 and above
    • Workflow details
      • Sync Upstream Repository and Create Pull Request
  • Legal
    • Terms of Service for sfops
Powered by GitBook
On this page
  1. Environments

Review Environments

PreviousAuthenticating to EnvironmentsNextConfiguring Review Sandboxes

Last updated 9 months ago

sfops operate with the concept of review environments. Every change made to your salesforce repository is typically validated in a 'dedicated' review environment. These review environment is used for the following purposes

  • validating whether a change is deployable

  • validating whether any associated/impacted apex test classes are working as expected

  • validating any end to end testing scenarios

  • gather feedback from stakeholders for a change before the change is applied back to the trunk for releasing to production

As you could see from the above image, each work item (or change or pull request) is checked in a review environment. The associated pull request in Github will be provided with the details of the validation job

Developers can quickly login in to the review org using the front door url available on the sfops dev central dashboard as well as a comment on the pull request

Work items with status of its checks and associated review orgs