A housing authority wants Foundry project builds to ride the existing municipal CI/CD pipeline. What integration should they implement?

A housing authority that wants Foundry project builds to ride the existing municipal CI/CD pipeline should wire Foundry build and deployment steps into that pipeline for repeatable delivery. Government change control favors gated, automated promotion over ad-hoc file movement. Integrating Foundry with CI/CD is how agents and apps promote with the same auditability, approvals, and rollback expectations as other municipal software releases.

Publish Foundry project outputs to a versioned artifact store for pipeline retrieval on schedule fails because it is not wired into the municipal CI/CD pipeline—it just stages artifacts for later retrieval, so it lacks the gated, repeatable deployment the authority needs. Sync Foundry prompt versions to municipal Git repo using timed exports alongside deployment stages fails because it only exports prompts to Git on a timer rather than wiring Foundry build and deployment steps into the CI/CD pipeline itself. Link municipal CI/CD pipeline status to Foundry evaluation jobs for scoring model quality before release stages fails because it adds an evaluation scoring step instead of integrating Foundry project build and deployment steps into the municipal CI/CD pipeline.

Exam caveat: CI/CD integration must include secrets handling, environment approvals, automated checks, and rollback—not only publishing to an artifact store, syncing prompts to Git, or linking evaluation jobs.

Operational check: run a pipeline that builds and validates a Foundry change, require an approval gate into production, and confirm the deployed agent version is identifiable in logs and release records.