Introduction
Understanding organizationsUnderstanding componentsManage organizationsManage componentsManage component Jira integrations
Set up your first organizationUnderstanding users and teamsUnderstanding role-based access controlManage usersManage teamsConfigure role-based access controlRBAC permissions reference
Understanding authentication in CloudBees UnifySet up multifactor authenticationConfigure SAML single sign-onConfigure OIDC authenticationConfigure network security policiesNetwork security reference
Understanding platform configurationUnderstanding environmentsManage properties and secretsManage environmentsTrack environment inventoryConfigure containersSet up preconfigured actionsConfigure notifications
Accessibility policy referenceShared responsibility model referenceSubscription and services agreementSupport policiesSupported browsers and external tools
Introduction
Understanding feature managementUnderstanding Configuration as CodeGet started with feature managementCreate and manage feature flagsConfigure feature flag targetingOrganize feature flagsImplement feature flag governanceConfiguration as Code reference
Understanding flag impressions and activity statusUnderstanding flag healthUnderstanding code referencesReview and clean up feature flagsSet up code references
Understanding Jira integration for feature flagsSet up the Jira integrationLink Jira tickets to feature flags
Understanding multiple SDK keysBuild your first mobile app with feature flagsBuild your first feature-flagged web applicationBuild your first feature-flagged backend serviceInstall client-side SDKsInstall server-side SDKsConfigure multiple SDK keysMobile SDK referenceWeb SDK referenceBackend SDK referenceClient SDK referenceFlag implementation reference
Introduction
Understanding CI workflowsCreate a build workflowCreate and manage workflowsCreate reusable workflowsTest and validate containers in workflowsCheck out source codeTrigger workflows remotelyWorkflow syntax referenceJobs syntax referenceSteps syntax referenceServices syntax reference
Monitor workflow runsView test results in runsView evidence in runsView deployments in runsManage workflow artifactsPublish test resultsPublish evidence itemsGenerate a software bill of materialsManage ServiceNow change requests
Configure workflow credentialsConfigure AWS credentialsConfigure container registry credentialsConfigure Git credentialsIntegrate external secret providers
Understanding GitHub Actions integrationSet up GitHub Actions integrationDisplay GitHub Actions workflows and runsRegister GHA build artifactsPublish GHA deployed artifactsPublish GHA test resultsPublish GHA evidence itemsTrigger CloudBees workflows from GitHub ActionsScan with GitHub Actions
Understanding CloudBees CI and Jenkins® integrationConnect CI and Jenkins controllersMonitor CI and Jenkins buildsRegister CI build artifactsRegister CI deployed artifactsPublish CI test resultsConfigure CI security scanningCI and Jenkins integration reference
Build and publish container imagesUnderstanding external CI/CD integrationsRun external CI/CD jobsExternal CI/CD action reference
Introduction
Understanding release orchestrationManage applicationsCreate deployer workflowsCreate staged workflowsCreate and manage releasesOrchestrate multi-workflow releasesRelease management reference
Understanding artifact managementRegister and track artifactsStore and retrieve artifactsPromote artifactsGenerate a software bill of materialsArtifact management reference
Deploy with HelmDeploy to KubernetesContainer deployment reference
Deploy to AWSAWS deployment reference
Deploy with enterprise platformsExecute remote deployment commandsEnterprise deployment reference
Verify deployments with New RelicDeployment verification reference

Get started with release orchestration

2 minute read

Set up your first coordinated release to see how CloudBees Unify manages multi-component deployments with approvals and monitoring. This walkthrough shows you the basic release orchestration workflow using existing components and environments.

Prerequisites

Before you begin, ensure you have:

  • A CloudBees Unify organization with release orchestration access (Edition 2 required).

  • At least one component with workflows configured.

  • Basic familiarity with environments and deployment concepts.

  • SCM integration already established.

For complete technical requirements, refer to CloudBees Unify technical requirements reference.

Create your first coordinated release

  1. Ensure you have components ready for release coordination.

    Navigate to Software Delivery  Components and verify you have at least one component with working workflows. If needed, create a component linked to a repository with basic CI/CD workflows configured.

  2. Define your deployment environments.

    Navigate to Configurations  Environments and create environments that represent your deployment stages. Create at least a "staging" and "production" environment to demonstrate release progression.

  3. Set up an application to group related components.

    Navigate to Software Delivery  Applications and create an application. Link your components to this application to enable coordinated release management across multiple services.

  4. Create your first release definition.

    1. From your application view, select Create Release.

    2. Define the release workflow including the components, versions, and target environments.

    3. Configure any approval requirements or manual steps needed for governance.

  5. Execute the release and monitor progress.

    1. Initiate the release execution from the application dashboard.

    2. Monitor the release progress through the CloudBees Unify release dashboard.

    3. Observe how CloudBees Unify coordinates deployment across components and environments.

    4. Review any approval workflows or manual intervention points during execution.

  6. Review release evidence and audit trail.

    After completion, examine the release dashboard to see deployment evidence, approval history, and execution timeline. CloudBees Unify provides comprehensive audit trails for compliance and post-deployment analysis.

Your application now has release orchestration configured for coordinated deployments with governance controls.

Understanding release coordination

The release orchestration setup demonstrates key coordination patterns:

  • Application-level release management that groups related components for coordinated deployment.

  • Environment progression with controlled advancement through deployment stages.

  • Approval workflows that provide governance and risk management for production deployments.

  • Release monitoring with centralized visibility into multi-component deployment status.

What you accomplished

You’ve experienced the basic release orchestration workflow:

  • Multi-component coordination through application-level release management.

  • Environment-aware deployment with controlled progression between stages.

  • Approval workflow integration that provides governance without blocking automation.

  • Release audit trails for compliance and post-deployment analysis.

This foundation enables you to explore advanced release orchestration features like complex approval chains, release templates, and automated rollback strategies.

Next steps for production releases

To implement release orchestration for production scenarios:

  • Design your environment progression strategy and approval requirements.

  • Configure release templates for repeatable deployment patterns.

  • Set up notifications and monitoring integration for release awareness.

  • Establish rollback procedures and emergency release processes.

Related pages

Get started with feature management
CloudBees Unify technical requirements reference