Repository navigation
Deploy test automatically and queue production approval - #565
Merged
Merged
Conversation
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pushes to
masternow build, test, and deploy totest. After test deployment and health checks succeed, production waits for approval in the sameCI/CDrun. Choose Review deployments → prod → Approve and deploy to build, test, and deploy that run's commit to production. A separate manual run is no longer required.Production requires approval from either
srkirklandor a member of@ucdavis/caesdo-devs. Self-approval is allowed, administrator bypass is disabled, and deployments are restricted tomaster. Failed, cancelled, or incomplete test deployments block the automatic production stage. Manual test/prod runs remain available for targeted retries; manual production still requires approval. Pull requests only validate.The shared deployment workflow preserves .NET 6, Node 22, Windows hosting, both WebJobs, and the existing publish/ZIP/deploy flow. Production uses its separate App Service-scoped OIDC identity. The runbook covers approval, selecting the intended commit, verification, and rollback; the Azure manual release path remains available.
Validation:
No merge or deployment was performed. Hosted approval-wait enforcement and post-deployment acceptance remain deferred to an authorized release.