Here are some examples:

Only execute for the```master``` branch:

{% highlight yaml %}

build-step:

description: Building the image.

Only execute for branches whose name begins with```FB-``` prefix (feature branches):

{% highlight yaml %}

build-step:

description: Building the image.

Ignore the develop branch and master branch:

{% highlight yaml %}

build-step:

description: Building the image.

Here are some examples. Execute if the string```[skip ci]``` is not part of the main repository commit message AND if the branch is```master```

{% highlight yaml %}

build-step:

description: Building the image.

Execute if the string```[skip ci]``` is not part of the main repository commit message, OR if the branch is not a feature branch (i.e. name starts with FB-)

{% highlight yaml %}

build-step:

description: Building the image.

{% endraw %}

{% endhighlight %}

This pipeline will run integration tests during the freestype step called`my_integration_tests` and at that point a Redis instance will be available at hostname`my-redis-db-host` and port 6479.

This pipeline will run integration tests during the freestype step called`my_integration_tests` and at that point a Redis instance will be available at hostname`my-redis-db-host` and port 6479. Note how in this example, the service container is placed at the root of the pipeline (as opposed to inside a specific step). This ensures that the Redis instance is running for[the duration of the pipeline]({{site.baseurl}}/docs/codefresh-yaml/service-containers/#running-services-for-the-duration-of-the-pipeline).

Like Docker compose it is possible to launch multiple services this way. For example let's say that a Java application needs both Redis and MongoDB during integration tests. Here is the respective pipeline:

Like Docker compose it is possible to launch multiple services this way. For example, let's say that a Java application needs both Redis and MongoDB during integration tests. Here is the respective pipeline:

{% highlight yaml %}

max-width="70%"

%}

This makes very easy to reuse compositions that you have already defined for other reasons in the Codefresh UI.

This makes very easy to reuse compositions that you have already defined for other reasons[in the Codefresh UI](https://codefresh.io/docs/docs/testing/create-composition/).

{% endraw %}

{% endhighlight %}

Here a Dockerfile for abackedn application is built on the spot and then is launched as sidecar container in the next step (with a hostname of`my_backend_app`). Notice that the`image` property in the sidecar service actually refers to a[Codefresh variable]({{site.baseurl}}/docs/codefresh-yaml/variables/) that holds the name of the build step.

Here a Dockerfile for abackend application is built on the spot and then is launched as sidecar container in the next step (with a hostname of`my_backend_app`). Notice that the`image` property in the sidecar service actually refers to a[Codefresh variable]({{site.baseurl}}/docs/codefresh-yaml/variables/) that holds the name of the build step.

We then run a`curl` command against the sidecar container to verify the correct health of the application. This is a great way to run integration tests against multilple microservices.