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. IssueOps
  2. Release

Release a Domain

PreviousReleaseNextHotfix Workflow

Last updated 1 year ago

The above diagram describes the "Release a Domain" workflow. This workflow is triggered by creating an issue or by clicking the "Initiate Release" from the dashboard.

This workflow then proceeds to fetch all the environments that are marked with "type:release" and proceeds to execute a dry run of the command in parallel across all release environments. The output of the dry run will be available as a comment in the Github issue created. The team could have a final check on the deployment plan that will be executed by sfops before proceeding for the actual execution.

The release environments typically is configured with "Required Reviewers" () and would need the respective environment owners to approve a release. Please note required reviewers are not required for the pre-release/ dry run check

https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment#required-reviewers
Release a domain workflow
Initiating a release from the sfops dashboard