Deploy a tested release to staging or production. A release captures file versions. A deployment makes that release available in an environment.
Before you deploy
Test the changed behavior in your project. Identify the environment that should receive the change and confirm its required variables and secrets are configured.
If the project requires a Git review, complete that review before the production deployment. Configure the environment before deploying. For automated delivery, use Deploy from CI.
Publish the current project
Save your project changes, then open Publish in the project workspace header. Select the environment or environments that should receive the current branch and select Deploy.
Studio creates a release from the active branch and then creates deployment records for the selected environments. If Studio reports unsaved files, return to the editor and resolve those changes before publishing again.
The Publish control requires deployment permission. Confirm the branch and selected environments before deploying.
Deploy an existing release
To use a version already captured, open Releases, find that release, and choose Deploy. Select the target environments and confirm. The same release can be deployed to several environments.
The action is available only for a deployable release and a user with deployment permission. Inspect the release's preparation state if it isn't available.
Open Deployments to inspect the deployment attempts. For failures, follow the linked release and check Logs.
Verify the deployed result
Open the deployed project or run the agent through the intended environment. Repeat a test that exercises the change, rather than relying only on the deployment status.
For an instruction change, send the same requests used before deployment and compare the output format and behavior. For a tool change, inspect its call and result in Runs.
Hand a Studio change to Git
When Studio is the editing workspace and Git is the review path, publish the completed change to a non-production environment to create its immutable release. Then follow Move Studio changes into Git to review the release through a pull request before production deployment.
Next
- Debug a run: Investigate runtime or agent issues after deployment.