Source Configuration
The Source stage defines where your application code or container image comes from. Click on the Source node in the workflow builder to open the configuration panel.
Source Type
Select the source type based on your setup:
| Source Type | Description |
|---|---|
| Git Repo | Build from source code stored in a Git repository. Atmosly will clone the repo, build a Docker image, and deploy it. |
| Container Registry | Deploy a pre-built image directly from a container registry. No CI build occurs. |
Git Repository Configuration
When using Git Repo as the source type:
Git Account
Select your Git hosting service from the connected integrations:
- GitHub
- GitLab
- Bitbucket
If you are editing an existing workflow linked to a deployed environment, the Git account and repository fields may already be pre-populated from the environment configuration.
Repository
Select the specific repository containing your application source code.
Branch Configuration
Choose how the pipeline determines which branch to build from:
| Option | Description |
|---|---|
| Branch | Select one or more specific branches (e.g., main, develop). The pipeline will build from the selected branch. |
| Tag | Specify a Git tag to use for builds. |
| Pull Request | Trigger the pipeline automatically when a pull request is created or updated. |
| Wildcard Branch | Define a glob pattern to match branch names dynamically. For example, release/* matches release/v1.0, release/v2.0, etc. feature-* matches feature-auth, feature-ui, etc. |
Trigger Type
| Type | Description |
|---|---|
| Automatic | Builds are triggered automatically via webhook when code is pushed to the matching branch. Requires a webhook to be configured on the Git repository. |
| Manual | Builds must be initiated manually by clicking Update & Execute Now in the workflow builder. |
When using Automatic trigger with Wildcard Branch, the webhook will match any pushed branch that fits the pattern — useful for triggering builds across feature or release branches without configuring each one individually.
Container Registry Configuration
When using Container Registry as the source type:
| Field | Description |
|---|---|
| Container Registry | Select from your connected registries (ECR, DockerHub, GCR, or GAR). |
| Image Repository | Select the image repository within the registry. |
| Image Tag | Select the specific image tag to deploy. |
The workflow will skip the Build and Push stages and deploy the selected image directly.
Saving the Configuration
Click Save at the bottom of the panel to apply your source configuration. The workflow builder will update to reflect the configured source stage.