-title:Promotion setup guidelines

url:"/create-promotion-sequence"

-title:Promotion Flows

url:"/promotion-flow"

url:"/promotion-flow"

-title:Promotion Policies

url:"/promotion-policy"

-title:Promotion Workflows

url:"/promotion-workflow"

url:"/promotion-workflow"

-title:Service accounts for Promotion Workflows

url:"/service-accounts-promotion-workflows"

-title:Promotion hooks

url:"/promotion-hooks"

-title:Promotion contexts in promotion hooks

url:"/promotion-context-promotion-workflows"

-title:Product promotion settings

url:"/product-promotion-props"

-title:Promotion entity YAMLs

-title:Promotion setup guidelines

url:"/create-promotion-sequence"

-title:Promotion Flows

url:"/promotion-flow"

url:"/promotion-flow"

-title:Promotion Policies

url:"/promotion-policy"

-title:Promotion Workflows

url:"/promotion-workflow"

-title:Service accounts for Promotion Workflows

url:"/service-accounts-promotion-workflows"

-title:Promotion hooks

url:"/promotion-hooks"

-title:Promotion contexts in promotion hooks

url:"/promotion-context-promotion-workflows"

-title:Product promotion settings

url:"/product-promotion-props"

-title:Promotion entity YAMLs

1.[Configuration Runtime]({{site.baseurl}}/docs/installation/gitops/configuration-runtime/)

The Configuration Runtime is a GitOps Runtime that stores promotion-related entities.

The Configuration Runtime is a GitOps Runtime that storesconfiguration for GitOpspromotion entities.

* Designate at least one GitOps Runtime as the Configuration Runtime.

* If no GitOps Runtime has been designated as such, Codefresh assigns one of the existing Runtimes.

1.[User permissions]({{site.baseurl}}/docs/administration/account-user-management/gitops-abac/)

Users need permissions to create Promotion Workflows, configure promotion settings for products, and trigger promotions.

1.[Create environments]({{site.baseurl}}/docs/environments/create-manage-environments/#create-environments)

Environments define the starting point and destination of promotions.

A promotion requires at least two environments:

* Triggerenvironment, the source of the changes being promoted

* TriggerEnvironment, the source of the changes being promoted

* Target environment, to which to promote the changes

1.[Create applications]({{site.baseurl}}/docs/deployments/gitops/create-application/#create-an-argo-cd-application)

1.[Create Promotion Workflows]({{site.baseurl}}/docs/promotions/promotion-workflow/)

Promotion Workflows (Argo Workflows) automate environment-specific tests and validations before and after promotion.

* Create and use Promotion Workflows to run smoke tests, database validation, and other requirements to verify readiness.

* Create Promotion Workflows to run smoke tests, database validation, and any other requirements to verify readiness of each application in an environment.

1.[Create Promotion Workflows with hooks]({{site.baseurl}}/docs/promotions/promotion-hooks/)

Promotion hooks provide promotion status and custom information for releases and environments during the Promotion Flow.

* Create hooks in Promotion Workflows to implement actions such as Slack notifications

* Define and export promotion contexts in hooks to expose and pass custom parameters such as Jira ID

1.[Define Promotion Policies]({{site.baseurl}}/docs/promotions/promotion-policy/)

Promotion Policies govern promotion behavior for environments enforcing rules, checks, and validations.

* Define policies that combine Promotion Workflows with promotion actions such as commits, pull requests

* The policy mechanism merges relevant settings from global policies according to priority, enforcing automated governance

1.[Create Promotion Flows]({{site.baseurl}}/docs/promotions/promotion-flow/)

Promotion Flows orchestrate the sequence of actions required to move and deploy changes through multiple environments.

* Automatically integrate environments, products, Promotion Workflows, and Promotion Policies into a structured promotion process

* Assign promotion hooks to track release and environment statuses for product releases

* Reuse Promotion Flows across products for consistent and reliable promotions

1.[Customize promotions for products]({{site.baseurl}}/docs/promotions/product-promotion-props/)

After setting up promotion entities, configure additional promotion settings at the product level.

* Promotion Templates to define attributes to be promoted across the product's applications

* Promotion Flows valid for the product and trigger conditions for each flow

1.[Trigger promotions]({{site.baseurl}}/docs/promotions/trigger-promotions/)

Trigger the promotion manually or automatically.

1.[Monitor promotion releases for products]({{site.baseurl}}/docs/promotions/product-releases/)

Monitor deployment progress as applications move through the promotion sequence.

* Use the Releases feature for products to monitor deployments

Releases in Codefresh GitOps offer a consolidated view of the deployment lifecycle for a product as it progresses through environments during a promotion. They enable you to track, visualize, and analyze changes from the initial trigger to the final deployment, providing comprehensive insights for all stakeholders.

A release is automatically created whenever a promotion is triggered for a product, either manually or through an automated flow. This ensures every change is documented and linked to its promotion lifecycle, giving teams complete visibility into their deployment processes.

In the context of GitOps, a release captures the progression of a product as it is promoted through environments. The release reflects the collective state of all environments and workflows involved in deploying a change, from the initial trigger to the final target environment, whether production or another specified target.

%}

Whether you are a product manager or an application developer,Releases offer:

Whether you are a product manager or an application developer,releases offer:

* Lifecycle visualization: Clearly track the deployment lifecycle of a product

* Integrated change list: Access a unified list of changes leading to a deployment

* Deployment status: Monitor ongoing deployments and quickly identify issues

Track the release visually to monitor its progression through each phase of the promotion lifecycle across environments.

SpecificRelease views centralizes all information, allowing you to:

Release views centralizes all information, allowing you to:

* Identify and resolve deployment issues without switching between tools

* Access everything you need to troubleshoot errors in one place.

See[Analyze change history in Release Notes](#analyze-change-history-in-release-notes).

The Releases tab for a product displays the releases for that product, whether successful or failed.

The header in the Releases page summarizes the change that triggered the promotion, the overall status of the release, and the count of failed, successful, running, and pending environments.

The commit details are always for thetrigger environment that initiated the promotion.

The commit details are always for theTrigger Environment that initiated the promotion.

{% include

image.html

The graphical view of the different environments defined in the PromotionFlo allows you to:

* Understand the interconnections between the environments, whether sequential or parallel.

The graphical view of the different environments defined in the PromotionFlow allows you to:

* Understand the interconnections between the environments, whether sequential or parallel

* Visualize the dependencies between environments to see how changes propagate through the deployment process

Each environment is color-coded to indicate the overall status of the promotion for that environment.

For example, if an update in the`staging` environment triggers the`echo-pre-action` Pre-Action Workflow, and a later update in the same environment also triggers the same`echo-pre-action` Pre-Action Workflow, the earlier instance is terminated, and the later instance continues to run.

The**Show/Hide Hooks** toggle button in the Release view displays/hides the[promotion hooks]({{site.baseurl}}/docs/promotions/promotion-hooks/) assigned to the Promotion Flow.

</tr>

<tr>

</tr>

<tr>

</tr>

<tr>