Back to Tech landscape

GitLab

Cloud & DevOps

DevOps platform with Git and CI/CD

Official documentation (opens in a new tab)

Overview

GitLab appears when clients run self-hosted or SaaS GitLab for source control and CI—Azure DevOps remains the ConnectSoft Factory default, with GitHub common for OSS mirrors.

Microsoft Azure is our primary cloud: Factory templates deploy to App Service, AKS, Container Apps, and managed data services with Bicep or Pulumi, Azure DevOps pipelines, and Application Insights baked in from day one.

When engagements require hybrid or multi-cloud tooling, we adopt it with explicit landing zones, least-privilege identities, and runbooks—while keeping Azure the anchor for ConnectSoft-generated platforms.

From first commit to production dashboards, our DevOps path favors repeatable infrastructure, managed identities, and measurable SLOs—so releases stay boring in the best way.

Why we use it:

  • Runner security and secret scopes
  • Pipeline as code in `.gitlab-ci.yml`
  • Integration boundaries to Azure pipelines
  • Mirror strategy if dual remotes exist
  • Infrastructure as code with environment-specific parameters
  • Managed identities and private networking in production paths
  • Integrated CI/CD through Azure DevOps and quality gates

Ready to work with us?

Let's discuss how our team can help achieve your digital goals