The Enterprise Rollout page shows environment health across the organizations in your enterprise and helps you find organizations that need a blueprint or a build fix.
For the environment model behind these metrics, see Enterprise environment management and declarative environment configuration.
Summary metrics
The page summarizes:
Organization health
The organization table includes:
The table sorts organizations that need attention first: broken environments, then organizations with no recent build, then healthy organizations.
Use the table to identify:
- Organizations with no blueprint or declarative repositories.
- Organizations with
partial or failed builds.
- Organizations whose last successful build is stale.
Phased blueprint adoption
Use the health data to adopt blueprints in controlled phases:
1. Validate the enterprise baseline
Create and validate an enterprise-tier base blueprint with the tools, runtimes, certificates, and shared configuration every organization needs. Confirm that its build succeeds and that a representative session can use the resulting environment.
See Enterprise environment management for the blueprint hierarchy and shared configuration guidance.
2. Add organization and repository configuration
After the enterprise baseline is healthy, configure organization blueprints for team-level tools and repository blueprints for project-specific dependencies and commands. Start with representative organizations and repositories, then expand to the rest of the enterprise.
Use environment blueprints to author and review the configuration.
3. Monitor build health
Return to the Rollout page after each adoption phase. Investigate organizations with missing blueprints, degraded or failed builds, and stale successful-build timestamps. Fix the relevant enterprise, organization, or repository blueprint, then confirm the next build returns to a healthy status.
Treat a passing build as a checkpoint, not the end of validation. Start a real Devin session for representative repositories and verify that tools, dependencies, network access, and project commands work as expected.
