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

Build & Deploy (CI/CD)

Biztraak can automate build → test → deploy workflows using a configured source-control integration.
Runner placement, provider support, and deployment behavior depend on the selected project workflow and available integrations.

Key Concepts

  • Pipelines: configured source changes can run through a pipeline tied to your component.
  • Runner placement: the selected integration determines where build and deployment compute runs.
  • Deployment stages: configured Git pipelines can use Build Reviews and promotion stages.
  • Traceability: available job, artifact, and deployment records can be reviewed in the platform.

Workflow

  1. Commit or PR

    • Pushes can trigger pipelines when the repository and workflow are configured for that behavior.
    • Branch promotion and Build Review behavior depend on project settings.

  2. Pipeline Jobs

    • Install → dependencies installed.
    • Build → code compiled, packaged, or containerized.
    • Test → optional unit/integration tests.
    • Deploy → push live to the deployed infra.

  3. Outputs

    • Logs for every stage.
    • Build artifacts available for inspection.
    • Deployment outputs: URLs, IPs, ports, repo links.

Customization

  • Pipeline Overrides: projects using the managed GitLab workflow can modify the generated .gitlab-ci.yml for custom steps. Other integrations expose their own pipeline configuration. See Capabilities and Availability.
  • Secrets Injection: env vars managed securely by Biztraak.
  • Configured workflows: use the source-control and deployment options exposed by the selected project configuration. See Capabilities and Availability for integration differences.

Roadmap

  • Cross-Provider Pipelines: run jobs across multiple clouds in one workflow.
  • Custom CI orchestration (Roadmap): extend pipeline orchestration beyond the integrations currently exposed by the project configuration.
  • Advanced Policies: enforce deployment approvals, compliance gates, and cost thresholds before release.

Why Biztraak CI/CD?

  • Integrated: connect Git source, build, and deployment stages through the project pipeline.
  • Configurable: runner and deployment placement follow the selected integration.
  • Traceable: available pipeline activity and deployment context can be reviewed together.
  • Flexible: override defaults, add steps, or integrate with external tools.

Example

  1. Developer pushes a commit to feature-login.
  2. Biztraak runs pipeline on AWS runner inside the team’s account.
  3. A Build Review spins up → feature-login.review.biztraak-hosting.com.
  4. PR merged into main → pipeline promotes to production.
  5. Audit trail updated with build + deploy events.

Next steps

  • GitLab → the optional managed GitLab repository and pipeline workflow
  • Build Reviews → preview environments for every commit
  • Deployments → understand deployment lifecycles
  • Web Services → detailed guide for Docker + ECS deployments

Biztraak brings source, build, and deployment context together through the configured project pipeline. See Capabilities and Availability for source-control differences.