Source Control
Connect a project to the Git provider your team already uses, or choose the managed GitLab option when you want Biztraak to manage the repository path. Each provider has its own repository, pipeline, and review workflow.
Provider support
| Capability | GitHub | GitLab.com | Self-hosted GitLab | Bitbucket |
|---|---|---|---|---|
| Connect and browse repositories | Available | Available | Available | Available |
| Trigger and view pipeline status | Available | Available | Available | Available |
| Manage pipeline variables and operations | Available | Available | Available | Available |
| View repository status | Available | Available | Available | Available |
| Pull or merge request workflows | Available | Available | Available | Available |
| Account connection and token renewal | Available | Available | Available | Available |
| Container image workflows | Available | Available | Available | Available |
| Runner credential setup | Available | Available | Available | Available |
| Keep the application repository with this provider | Available when selected for the project | Available when selected for the project | Available for the managed GitLab-compatible path | Limited by the current Bitbucket pipeline experience |
| Pipeline experience in the product | Available through the selected project workflow | Available through the selected project workflow | Available through the selected project workflow | Not currently available in the default product experience |
Azure DevOps is not currently available as a project source-control option.
Repository placement
The repository containing your application code and the repositories Biztraak creates for platform-managed dependencies can be different.
| Project situation | Your application repository | Platform-generated components and dependencies |
|---|---|---|
| Managed GitLab selected | Stored and operated in the configured managed GitLab instance | Managed GitLab-backed repositories can be provisioned when required |
| GitHub, GitLab.com, or another external provider selected | Remains with the selected provider and is not imported or cloned into managed GitLab unless you explicitly select import | Deployment dependencies can still receive managed GitLab-backed repositories when their deployment path requires them |
| Bitbucket with the current pipeline experience unavailable | The current project flow uses the managed GitLab import path for the Bitbucket pipeline limitation | Managed GitLab-backed repositories are used for the imported pipeline path |
Repository placement depends on the provider, repository visibility, import choice, and project workflow.
Pipeline formats and runners
Each provider uses its own pipeline format:
| Provider | Pipeline format | Execution path |
|---|---|---|
| GitHub | GitHub workflow | GitHub Actions integration |
| GitLab.com | GitLab CI | GitLab pipeline integration |
| Self-hosted GitLab | GitLab CI | Self-hosted GitLab pipeline integration |
| Bitbucket | Bitbucket pipeline | Bitbucket pipeline integration, subject to the current product experience and repository mode |
The managed GitLab option uses a root .gitlab-ci.yml entrypoint and generated component files. GitHub and Bitbucket use their own workflow or pipeline files.
Common repository and runner modes
| Mode | Repository location | Pipeline execution |
|---|---|---|
| Managed GitLab | Configured managed GitLab instance | Managed GitLab pipeline path |
| External GitHub or GitLab | Selected external provider | Provider pipeline path, with managed runner choices where available |
| External Bitbucket | Selected external provider when the direct path is available | The current default flow uses the managed GitLab import path because the Bitbucket pipeline experience is not currently available |
| Self-hosted GitLab | Selected self-hosted GitLab instance | Self-hosted GitLab pipeline path |
The location of a platform-generated dependency repository can differ from the location of your application repository within the same project.