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. self managed instances
  2. Setup for self managed instances

5. Setting up project repository

Previous4. Trigger the workflowsNext6. Fetching upstream changes

Last updated 11 months ago

In your project repository, please ensure you set up the following GitHub repository variables and secrets.

VARIABLE
VARIABLE_TYPE
VALUE_TYPE
EXAMPLE
Comments

SFOPSBOT_APP_ID

REPOSITORY_VARIABLE

STRING

418222

The id of the GitHub created in

SFOPSBOT_APP_PRIVATE_KEY

REPOSITORY_SECRET

STRING

<private_key>

The private key of the GitHub created in

SFOPS_DASHBOARD_REPO

REPOSITORY_VARIABLE

STRING

<your-org-name>/<dashboard-repo>

The dev central repository associated with this project repository

SFOPS_ISSUETRACKER_URL_BASE

REPOSITORY_VARIABLE

STRING

https://<jira_ur>

The Jira URL where the work items should be connected within this repository

SFOPS_ISSUETRACKER_WORKITEM_FILTER

REPOSITORY_VARIABLE

STRING

(FGK|FFK)-[0-9]{3,4}

The Issue URL regex string for connecting SFOPS with Jira

SFOPS_JIRA_USER

REPOSITORY_VARIABLE

STRING

username@jira.com

The username for the JIRA integration

SFOPS_JIRA_TOKEN

REPOSITORY_SECRET

STRING

<jira_token>

The Jira API token for integrating SFOPS to Jira

SFOPS_METRICS_PROVIDER

REPOSITORY_VARIABLE

STRING

datadog

The metric provider used by your project, It could be datadog, new relic or splunk

DEVHUB_SFDX_AUTH_URL

REPOSITORY_SECRET

STRING

<force://>?

The SFDX Auth URL of your deployment service account in the production

BRANCHES

REPOSITORY_VARIABLE

ARRAY

[ "main" ]

The active trunk where the build and release should be associated

These variables will be automatically set up during the set up of sfops in your repository by the FLXBL team. This guide is only applicable when you are setting up a self managed instance of sfops

step 2
step 2