Repositories & applications configuration

Overview

In Envtracker, you start by importing your Git repositories. Then you create applications by assigning a repository to one or more environments.

• A repository is the source template
• An application is an environment-specific instance of that repository

Import a repository

1. Connect Git (see Integrations configuration)
2. Import/select the repository you want to manage in Envtracker

During repository creation, you can either:

• Use the project Git configuration, or
• Create a repository-specific Git configuration right away

This is useful when a repository needs a different Git connection than the project default.

Create applications (assign repositories to environments)

After importing a repository, you can assign it to environments. Envtracker creates an application instance for each assignment.

This is how you manage the same repository deployed to multiple environments.

Configuration inheritance (template vs app override)

Applications are created with no custom configuration by default.

• If an application has no override, Envtracker uses the repository/template configuration
• If you override a setting at the application level, Envtracker uses the application configuration instead

What you can configure

Repository and application configuration use the same categories of settings.

Git and CI

Git and CI settings can be configured at the project level and overridden at the repository/template or application level.

Artifact version policy

Artifact version policy controls where Envtracker pulls application versions from.

You can configure multiple strategies. Common examples include:

• Git tags
• CI YAML
• pom.xml
• package.json
• Regex file
• Artifact file

When multiple strategies are defined, Envtracker uses them in the configured order.

Upgrade strategy

Upgrade strategy controls how Envtracker detects new, undeployed changes.

Supported approaches:

• Static source
  • Always pull changes from a fixed source (for example develop)
• Last deployed ref
  • Pull new changes relative to the last deployed branch or reference

Variables and parameters

Variables/parameters are key-value inputs used during deployments.

Supported types:

• Boolean
• Text
• Secret
• Options (selectable values at deploy time)

For each parameter you can configure:

• Default value
• Required or optional

Pipeline settings

Pipeline settings define the jobs Envtracker expects and how they run.

Each job includes:

• Code (identifier)
• Sequence
• Required or optional
• Sequential
  • Whether the job must wait for the previous job

Downstream pipelines (application only)

Downstream pipelines are an application-level setting.

They define additional pipelines that should run after the configured pipeline completes successfully.

You add them as a list (by name).

Deployable source settings

Deployable source settings define how Envtracker selects a pipeline/run to deploy from.

Deployment strategy

• Use last pipeline
• Create a new pipeline

Ready job status filters

Filter which job statuses count as ready. Examples include:

• created
• running
• pending

Pipeline status filter sequence

When Envtracker can use existing pipelines, it must search for a usable pipeline.

You can configure multiple status filters in a specific order. Envtracker checks them one after another until it finds a usable pipeline.

Where to search for pipelines

Choose where Envtracker looks for pipelines:

• Tags
• Branches
• Both

Pattern

Provide a pattern to limit which tags/branches Envtracker searches.