CI/CD governance: integrated CI/CD orchestration

Keep your CI/CD pipelines and add what they lack: committee approvals, environment gates, install evidence and an audit trail for every release.

2 min read

What a CI/CD pipeline does well

A CI/CD pipeline builds, tests and deploys code automatically and repeatably. It is the fastest, safest way to move software, and it is very good at the technical steps.

What a pipeline alone does not answer

Why this change was made and which requirement it delivers.
Who, by role, authorized it for pre-production and for production.
Whether the rollback plan was reviewed.
What evidence proves the installation was correct.
How the change did against its committed dates.

Integrated CI/CD orchestration

DevGob sits above the pipeline. It links the pull requests, CI runs and releases to the change, and governs the decisions between stages: entering testing, going to the committee, installing in pre-production and in production. Your pipeline keeps executing; DevGob keeps the record and the approvals.

A typical flow

The developer opens a pull request linked to the work item.
CI runs, and DevGob shows the result on the item.
The review is approved and the change enters testing.
QA records its results and the change goes to the Pre committee.
After installing in pre-production, the Production committee authorizes.
Production install evidence is attached and the change is done.

How DevGob helps

DevGob orchestrates the governance around your CI/CD: approvals by role between stages, install evidence and one auditable record per release.

Read it in the documentation

Frequently asked questions

Does DevGob deploy my application?

No. Deployment runs in your CI/CD tool. DevGob governs the authorization and records the evidence of each installation.

Can it stop a deployment?

DevGob holds the change in its flow until the committee authorizes it. Enforcing that inside the pipeline, for example with a manual approval step, is configured in your CI/CD tool.

Which CI/CD tools does it work with?

GitHub today; Azure DevOps and GitLab integrations are on the roadmap.

Continuous integration, connected to the work See the result of every CI run on the work item it belongs to: branches, commits, pull requests and GitHub Actions runs, linked automatically. Release management with approvals and evidence Manage software releases from development to production: phases with owners, Pre and Production committees, milestones and install evidence. DevOps with governance: deliver fast and stay in control A DevOps platform that plans the work and governs every change to production: backlog, sprints, committee approvals, install evidence and audit trail. DevGob vs GitLab GitLab is one DevSecOps application for code, CI/CD and security; DevGob governs changes with committees, business traceability and evidence.

DevOps with governance, on one record

DevGob plans the work and governs every change on its way to production: backlog, sprints, committee authorizations, install evidence and an audit trail.

Request a workspace Documentation