Integrations configuration

Overview

Integrations connect Envtracker to the tools your team already uses.

Git

Use Git integration to connect Envtracker to your Git provider.

Git-specific inputs

• Default branch
  • The branch Envtracker shows by default for deployments
• Remote workspace
  • Your Git provider workspace or namespace (for example GitHub organization, GitLab group, Bitbucket workspace)

Connector

Git uses a connector dialog that includes:

• Provider type: GitLab, Azure DevOps, Bitbucket, or GitHub
• API URL: your provider API base URL (works for hosted and self-managed)
• Authentication method
  • Basic auth: username + password
  • Token: personal access token or equivalent
  • Proxy: username + password + proxy URL
  • OAuth2: OAuth-based connection (when available)

CI

Use CI integration to connect Envtracker to your CI system.

Connector

CI uses the same connector pattern:

• Provider type: GitLab CI, Bitbucket Pipelines, Azure DevOps, or Jenkins
• API URL: your CI API base URL
• Authentication method
  • Basic auth: username + password
  • Token
  • Proxy: username + password + proxy URL
  • OAuth2 (when available)

Jira

Use Jira integration to connect your Jira projects and automate updates based on deployments.

Connector

Jira uses the same connector dialog style, but there is no provider type selection.

It includes:

• API URL
• API version
• Authentication method
  • Basic auth: username + password
  • Token
  • Proxy: username + password + proxy URL
  • OAuth2 (when available)

Jira projects and issue types

Once connected, Envtracker can pull:

• Your Jira projects
• Their issue types

Workflows per issue type

To enable automation, you create a workflow per issue type:

• Create a workflow for an issue type using a dialog (states + transitions)
• Update and maintain it using the canvas (node) view

You can then enable:

• Auto issue transitions
  • Automatically move issues through workflow transitions based on deployments
• Deployment comments on stories
  • Post deployment information as comments on related issues

Story filtering and commit tracking

To control what Envtracker imports and links:

• Story pattern (filter)
  • Filters which Jira stories are pulled into Envtracker
• Story pattern (commit tracking)
  • Defines how Envtracker recognizes commits that belong to a story, and which commits are considered untracked

AI

Use AI integration to connect an AI provider for features that require AI.

• Provider type: OpenAI, Anthropic, Google, or Azure OpenAI
• URL
• Model name
• Token

Project defaults and overrides (Git and CI)

Git and CI integrations support project-level defaults:

• The project configuration is used by default
• It can be overridden at the template/repository level or the application level when needed