PUBLIC ALPHABiztraak is now in public alpha. Share feedback
Biztraak
Git & CI/CD
Private GitLab Build & Deploy Pipeline Unit Tests Environment Variables Deploy Web Services Configure Web Services

GitLab Integration

Biztraak can use GitLab for source control, pipelines, and CI/CD automation.
The managed GitLab integration is one optional source-control path. Projects can also use the other integrations listed in Capabilities and Availability.

Unlike other platforms, Biztraak doesn’t hide your infra.
Runner placement and lifetime depend on the configured integration and project workflow.

Key Concepts

  • Platform-managed repositories: platform-generated components and deployment dependencies that use the managed GitLab path get their own repository in the configured Biztraak GitLab instance. In a deploy-from-repository project, the user-provided repository remains with its selected provider and is not imported or cloned into managed GitLab.
  • Workflow-specific infrastructure: the selected deployment integration determines where pipeline jobs run.
  • Deploy from Repo: the user-provided repository stays with its selected provider. It is not imported or cloned into managed GitLab unless the managed GitLab path is explicitly selected. Platform-generated dependencies can still receive managed GitLab-backed repositories when their deployment path requires them.
  • Access Control: tied directly to Team Members and Roles.
  • Traceability: available commit, pipeline, and deployment records can be reviewed in the project context.

Workflow

  1. Project Creation

    • From Template: repos are auto-provisioned in the configured Biztraak GitLab instance.
    • From Repo: your existing code stays in the selected source-control provider. Deployment dependencies that require platform-managed repositories can still be provisioned in the configured Biztraak GitLab instance.

  2. Development

    • Use Cloud Dev to edit in the browser.
    • Or clone repos locally using SSH/HTTPS.

  3. CI/CD Pipelines

    • Configured commits can trigger pipelines.
    • Branch review and production promotion behavior depend on project settings.

  4. Outputs & Logging

    • Pipelines produce logs, artifacts, and deployment outputs.
    • Available pipeline and deployment events are associated with the project record.

Other source-control options

The managed GitLab workflow is optional. Use Capabilities and Availability to compare the currently available GitHub, GitLab, self-hosted GitLab, and Bitbucket integrations.

Why GitLab?

  • Integrated: source and CI/CD context can be managed in one workflow.
  • Configurable: pipeline behavior follows repository and project settings.
  • Access-controlled: repository access follows the configured roles and integration.
  • Traceable: available commit and deployment records are kept in project context.

Next steps

With GitLab as a supported engine, Biztraak connects repository activity with configured build and deployment workflows.