url:"/deploy"

-title:Approval

url:"/approval"

-title:Conditional execution of steps

url:"/conditional-execution-of-steps"

-title:Post-step operations

url:"/post-step-operations"

-title:Triggers in pipelines

url:"/triggers"

sub-pages:

-title:Hooks in pipelines

url:"/hooks"

-title:Annotations in pipelines

url:"/annotations"

url:"/annotations"

-title:Conditional execution of steps

url:"/conditional-execution-of-steps"

-title:Post-step operations

url:"/post-step-operations"

-title:Grouping steps into stages

url:"/stages"

-title:Cachingfor pipelines

-title:Cachingin pipelines

url:"/pipeline-caching"

-title:Debugging pipelines

url:"/debugging-pipelines"

Before going any further make sure that you are familiar with the[basics of Codefresh pipelines]({{site.baseurl}}/docs/configure-ci-cd-pipeline/introduction-to-codefresh-pipelines/).

Before going any further make sure that you are familiar with the[basics of Codefresh pipelines]({{site.baseurl}}/docs/pipelines/introduction-to-codefresh-pipelines/).

Codefresh offers two modes of execution:

{% include

image.html

lightbox="true"

file="/images/codefresh-yaml/parallel-push.png"

url="/images/codefresh-yaml/parallel-push.png"

file="/images/pipeline/codefresh-yaml/parallel-push.png"

url="/images/pipeline/codefresh-yaml/parallel-push.png"

alt="Parallel Docker push"

caption="Parallel Docker push"

max-width="80%"

Also notice the`fail_fast: false` line in the unit tests. By default, if*any* steps fails in a pipeline the whole pipeline is marked as a failure. With the`fail_fast` directive we can allow the pipeline to continue so that other steps that depend on the failed step can still run even.

A pipeline step can also depend on multiple other steps.

title:"Annotations inCIpipelines"

title:"Annotations in pipelines"

description:"Mark your builds and projects with extra annotations"

group:pipelines

redirect_from:

* Builds

* Docker images

You can view/edit annotations using the[Codefresh CLI](https://codefresh-io.github.io/cli/annotations/) or directly in the Codefresh Web UI.

You can view/edit annotations using the[Codefresh CLI](https://codefresh-io.github.io/cli/annotations/){:target="\_blank"} or directly in the Codefresh Web UI.

see[hooks]({{site.baseurl}}/docs/pipelines/hooks/).

see[hooks in pipelines]({{site.baseurl}}/docs/pipelines/hooks/).

In the most basic scenario you can use the[post operations]({{site.baseurl}}/docs/pipelines/post-step-operations/) of any Codefresh[step]({{site.baseurl}}/docs/pipelines/steps/) to add annotations:

In the most basic scenario, you can use the[post operations]({{site.baseurl}}/docs/pipelines/post-step-operations/) of any Codefresh[step]({{site.baseurl}}/docs/pipelines/steps/) to add annotations:

{% highlight yaml %}

Apart from scalar values, you can also store more complex expressions in annotations. You have access to all[Codefresh variables]({{site.baseurl}}/docs/pipelines/variables/), text files from the build and even evaluations from the[expression syntax]({{site.baseurl}}/docs/pipelines/condition-expression-syntax/).

Apart from scalar values, you can also store more complex expressions in annotations. You have access to all[Codefresh variables]({{site.baseurl}}/docs/pipelines/variables/), text files from the build and even evaluations from the[expression syntax]({{site.baseurl}}/docs/pipelines/conditional-execution-of-steps/#condition-expression-syntax).

{% highlight yaml %}

{% endraw %}

{% endhighlight %}

The last two annotations add the text of a file as a value. You can define an absolute or relative path. No processing is done on the file before being stored. If a file is not found, the annotation will still be added verbatim.

We suggest you only store small text files in this manner as annotations values.

Note that this syntax is optional. You can still define annotations for a build/image or any other entity using the post operations of any step by mentioning explicitly the target id and type.

[Image annotations]({{site.baseurl}}/docs/docker-registries/metadata-annotations/)

[Post-step operations]({{site.baseurl}}/docs/pipelines/post-step-operations/)

[Creating CI pipelines]({{site.baseurl}}/docs/pipelines/pipelines/)

[Hooks in CI pipelines]({{site.baseurl}}/docs/pipelines/hooks/)

[Image annotations]({{site.baseurl}}/docs/pipelines/docker-image-metadata/)

[Creating pipelines]({{site.baseurl}}/docs/pipelines/pipelines/)

[Hooks in pipelines]({{site.baseurl}}/docs/pipelines/hooks/)

title:"Conditional execution of steps"

description:"Skip specific pipeline steps according to one or more conditions"

group:pipelines

sub_group:steps

redirect_from:

-/docs/codefresh-yaml/conditional-execution-of-steps/

-/docs/codefresh-yaml/condition-expression-syntax/

-/docs/conditional-execution-of-steps/

toc:true

For each step in a`codefresh.yml` file, you can define a set of conditions which need to be satisfied in order to execute the step.(An introduction to the`codefresh.yml` file can be found[here]({{site.baseurl}}/docs/codefresh-yaml/what-is-the-codefresh-yaml/).)

For each step in a`codefresh.yml` file, you can define a set of conditions which need to be satisfied in order to execute the step.For details on the`codefresh.yml` file, see[Pipeline definitions YAML]({{site.baseurl}}/docs/pipelines/what-is-the-codefresh-yaml/).)

There are currently two main methods to define conditions:

* Branch conditions

{% endhighlight %}

You can use the User Provided variables as explained in[Variables]({{site.baseurl}}/docs/pipelines/variables/), including the[variables

exposed by each individual pipeline step]({{site.baseurl}}/docs/pipelines/variables/#step-variables).

You can use the user-defined variables, including the variables exposed by each individual pipeline step. See[Variables in pipelines]({{site.baseurl}}/docs/pipelines/variables/).

[Codefresh YAML for pipeline definitions]({{site.baseurl}}/docs/pipelines/what-is-the-codefresh-yaml/)

[Variables]({{site.baseurl}}/docs/pipelines/variables/)

[Variables in pipelines]({{site.baseurl}}/docs/pipelines/variables/)

[Pull Requests and Branches]({{site.baseurl}}/docs/ci-cd-guides/pull-request-branches/)

In all cases the[shared Codefresh volume]({{site.baseurl}}/docs/pipelines/introduction-to-codefresh-pipelines/#sharing-the-workspace-between-build-steps) is automounted so you can examine your source code or any other intermediate artifacts placed in your project folder or the pipeline cache.

If the breakpoint is on a`before` or`after` phase, the command line terminal is powered by an[alpine](https://alpinelinux.org/) image. The image has already useful tools such as`wget`,`nc` and`vi`. If you have the advanced debugging capabilities in your Codefresh plan you can then install additional tools on your own directly in the terminal with[apk](https://wiki.alpinelinux.org/wiki/Alpine_Linux_package_management). Examples:

If the breakpoint is on a`before` or`after` phase, the command line terminal is powered by an[Alpine](https://alpinelinux.org/){:target="\_blank"} image. The image has already useful tools such as`wget`,`nc` and`vi`. If you have the advanced debugging capabilities in your Codefresh plan you can then install additional tools on your own directly in the terminal with[apk](https://wiki.alpinelinux.org/wiki/Alpine_Linux_package_management){:target="\_blank"}. Examples:

[Codefresh YAML for pipeline definitions]({{site.baseurl}}/docs/pipelines/what-is-the-codefresh-yaml/)

[Steps inCIpipelines]({{site.baseurl}}/docs/pipelines/steps/)

[Steps in pipelines]({{site.baseurl}}/docs/pipelines/steps/)

[Running pipelines locally]({{site.baseurl}}/docs/pipelines/running-pipelines-locally/)