Sleuth Documentation
HomeBlogSupportSign up
  • Getting started
  • Navigating Sleuth
  • DORA metrics
    • Deploy frequency
    • Change lead time
    • Change failure rate
    • MTTR
    • Interpreting Metrics in Sleuth
  • Deployment tracking
    • Organization
      • Labels
      • Trends
      • Compare
      • Search
      • Status
    • Projects
      • Issue trackers
    • Environments
    • Code deployments
      • Creating a deployment
      • How to register a deploy
      • Rollbacks
      • Automatic tagging
      • Deployment locking
      • Environment drift
      • Move code deployments
      • Search everything
    • Feature flags
    • Manual changes
    • Deploys
    • Teams
  • Work in Progress
  • Goals
  • Sleuth Automations
    • Automations Marketplace
      • Installing Automations
        • Installing PR "Update" Automations
      • Editing and uninstalling Automations
      • Smart suggestions
      • Understanding efficacy
    • Custom Automations
      • Automations Cookbook
      • Webhook Actions
      • Trigger Build Actions
        • Bitbucket Pipelines
        • CircleCI
        • Github Actions
        • Jenkins
  • Slack & Email Notifications
  • Auto-verify deploys
    • Anomaly detection
    • Error impact
    • Metric impact
  • Ignoring pull requests
  • Slack mission control
    • Approvals
    • Project notifications
    • Personal notifications
    • Search Sleuth in Slack
    • Project/Deployment history
    • Developer standup
  • Sleuth API
    • Deploy Registration
    • Deploy import
    • Manual Change
    • Custom Incident Impact Registration
    • Custom Metric Impact Registration
    • Deprecation information
    • GraphQL Queries
    • GraphQL Mutations
    • Query batching
  • Integrations
    • About Integrations...
    • Code integrations (read-only)
      • Azure DevOps
      • Bitbucket
      • GitHub
      • GitLab
      • Custom Git
      • Terraform Cloud
    • Code integrations (write)
    • Feature flag integrations
      • LaunchDarkly
    • Impact integrations
      • Error trackers
        • Bugsnag
        • Honeybadger
        • Rollbar
        • Sentry
      • Metric trackers
        • AppDynamics
        • AWS CloudWatch
        • Custom
        • Datadog
        • Jira metrics (Cloud / Data Center)
        • NewRelic
        • SignalFx
      • Incident tracker integrations
        • Blameless
        • PagerDuty
        • Datadog Monitors
        • Statuspage
        • Opsgenie
        • Jira (Cloud/Data Center)
        • FireHydrant
        • Rootly
        • ServiceNow
        • Custom
          • Grafana OnCall
      • CI/CD builds
        • Azure Pipelines
        • Bitbucket Pipelines
        • Buildkite
        • CircleCI
        • GitHub Actions
        • GitLab CI/CD Pipelines
        • Jenkins
    • Sleuth DORA App for Slack
    • Microsoft Teams integration
    • CI/CD integrations
      • Azure Pipelines
      • Bitbucket Pipelines
      • Buildkite
      • CircleCI
      • Github Actions
      • GitLab CI/CD Pipelines
      • Jenkins
    • Issue tracker integrations
      • Jira Cloud
      • Jira Data Center
      • Linear
      • Shortcut
    • Fixing broken integrations
  • Pulse
    • Welcome to Pulse docs
    • Quick Start setup guide
    • Beginner tutorials
      • 1. How to create a Teamspace
      • 2. How to create a Review
      • 3. How to create a Survey
  • Features
    • Reviews
      • Review workflow
      • Review templates
      • Widgets and Sections
        • Widget type
      • Review settings
    • Surveys
      • Survey Workflow
    • Teamspaces
    • Inbox
    • AI assistant
    • General settings
      • Users and Teams
      • Investment mix
  • Settings
    • Organization settings
      • Details
      • Authentication
        • SAML 2.0 Setup
          • Okta Configuration
          • Azure AD Configuration
          • PingIdentity Configuration
      • Access Tokens
      • Members
      • Team Settings
      • Billing
    • Project settings
      • Details
      • Slack settings
      • Environment settings
      • Code deployment settings
      • Feature flag settings
      • Impact settings
    • Account settings
      • Account settings
      • Notifications settings
      • Identities settings
    • Role Based Access Control
  • Resources
    • FAQ
    • Sleuth TV
    • Purchasing
    • About Sleuth...
Powered by GitBook
On this page
  • Adding a Code deployment
  • Edit Code Deployments
  • Mapping branches to environments
  • Advanced Settings
  • Source path prefix (include)
  • Source path prefix (excludes)
  • Automatically lock deployments
  • Slack notifications
  • Collect impact
  • Track builds with

Was this helpful?

  1. Settings
  2. Project settings

Code deployment settings

PreviousEnvironment settingsNextFeature flag settings

Last updated 6 months ago

Was this helpful?

The Code Deployments tab in is where configuration changes are made to the code deployment change sources in your project. Additionally, you can manage the mapping of your repositories and branches to your environments.

Adding a Code deployment

To add a code deployment, first make sure you have the necessary permissions.

Edit Code Deployments

Make changes as needed to your code deployment. On this screen, you can:

  • Select the code repository for your code deployment change source in the Repository dropdown.

  • Select the branch in the repository that you wish to use for the code deployment change source. Only branches in the repo selected above are displayed. Sleuth will, by default, select the master branch. If you use different branches to deploy to different environments see the Mapping branches section below.

  • Change the name of the code deployment, which is shown in the Code Deployments section of the sidebar.

Mapping branches to environments

By default Sleuth maps the master branch to all environments in your project. However, you can change this behavior if you used named branches for your other environments. For example, you might wish to deploy your master branch to production, which is the default behavior, and deploy your staging branch to your staging environment.

Advanced Settings

Additional configuration options allow you to fine-tune the behavior of Sleuth when it detects deploys via your change sources.

Source path prefix (include)

Restricts deployment information to only files matching the entered path prefix. This feature is especially useful for mono-repos.

In the example below, only files located in the sleuth/apps/pullrequests directory will be included in deploys. You can specify multiple paths to include by specifying a comma separated list of paths.

This can be used in conjunction with Source path prefix excludes, see below.

Source path prefix (excludes)

Restricts deployment information to only files not matching the entered path prefix. This feature is especially useful for mono-repos.

In the example below, only files not located in the sleuth/apps/pullrequests directory will be included in deploys. You can specify multiple paths to exclude by specifying a comma separated list of paths.

This can be used in conjunction with Source path prefix includes, see above.

Automatically lock deployments

Selecting this checkbox allows Sleuth to automatically lock a deployment when a pull request merged to your deployment branch (Sleuth will then unlock the code deployment once that change has deployed). Without this enabled, you can still lock a deployment manually in the Slack notification or in the Dashboard of the active project by clicking the Lock button.

Slack notifications

Collect impact

Track builds with

Build tracking is set at the project level. However, if you have a code deployment that uses an alternative build provider you can set that with this field.

See to see which source provider Sleuth supports.

To edit code deployments, click the edit dropdown in the Actions column then select **Edit **to view the Edit Code Deployment screen (shown below).

Select how Sleuth will track know when you've deployed. See for more details.

Selecting this checkbox lets Sleuth send Slack notification through the Sleuth DORA App for Slack. You can configure these notifications in the of Project Settings.

Selecting this checkbox lets Sleuth collect impact information collected through your . The information is collected, analyzed, then displayed in the deploy card of each deployment. You will need to configure these integrations in the error and metric impact tools themselves (i.e., Datadog, Sentry, Rollbar, etc.).

Code deployment
How to register a deploy
Slack Notifications tab
error and metric impact integrations
Project Settings
Code Deployments tab in Project Settings