<commit_before>---
title: Pushing an Application with Multiple Buildpacks
owner: Buildpacks
---

<strong><%= modified_date %></strong>

This topic describes how developers can push an application with multiple buildpacks.

For more information about pushing applications to Cloud Foundry, see the [Deploy an Application](../devguide/deploy-apps/deploy-app.html) topic.

##<a id='cfcli'></a> Specifying Buildpacks with the cf CLI

To push an application with multiple buildpacks using the Cloud Foundry Command Line Interface (cf CLI), perform the following procedure:

1. Ensure you are using the cf CLI v6.32.0+:
	<pre class="terminal">$ cf version
	cf version 6.32.0+0191c33d9.2017-09-26
	</pre>
	For more information about upgrading the cf CLI, see the [Installing the cf CLI](../cf-cli/install-go-cli.html)
1. Push the application with the binary buildpack with the `--no-start` flag:
	<pre class="terminal">$ cf push YOUR-APP --no-start -b binary_buildpack</pre>
1. Upgrade the application to multiple buildpacks, and specify the buildpacks:
	<pre class="terminal">
	$ cf v3-push YOUR-APP -b BUILDPACK-NAME-1 -b BUILDPACK-NAME-2
	</pre>
	To see a list of available buildpacks, run `cf buildpacks`.

If you are using an application manifest, you cannot include the `buildpack` key or future pushes will not function properly. 

For more information about using the cf CLI, see the [Cloud Foundry Command Line Interface](../cf-cli/index.html) topic.<commit_msg>update multi buildpack topic[#151522671]<commit_after>---
title: Pushing an Application with Multiple Buildpacks
owner: Buildpacks
---

<strong><%= modified_date %></strong>

This topic describes how developers can push an application with multiple buildpacks.

For more information about pushing applications to Cloud Foundry, see the [Deploy an Application](../devguide/deploy-apps/deploy-app.html) topic.

##<a id='cfcli'></a> Specifying Buildpacks with the cf CLI

To push an application with multiple buildpacks using the Cloud Foundry Command Line Interface (cf CLI), perform the following procedure:

1. Ensure you are using the cf CLI v6.32.0+:
	<pre class="terminal">$ cf version
	cf version 6.32.0+0191c33d9.2017-09-26
	</pre>
	For more information about upgrading the cf CLI, see the [Installing the cf CLI](../cf-cli/install-go-cli.html)
1. Push the application with the binary buildpack with the `--no-start` flag:
	<pre class="terminal">$ cf push YOUR-APP --no-start -b binary_buildpack</pre>
	This command pushes the application but does not start it.
1. Upgrade the application to multiple buildpacks, and specify the buildpacks:
	<pre class="terminal">
	$ cf v3-push YOUR-APP -b BUILDPACK-NAME-1 -b BUILDPACK-NAME-2
	</pre>
	To see a list of available buildpacks, run `cf buildpacks`.

	This command changes the buildpack and starts the application. 
	<p class="note"><strong>Note</strong>: The two-push workflow is currently required because only <code>v3-push</code> supports multiple buildpacks.</p>

Keep in mind the following about the `v3-push` command:

* `v3-push` currently only supports a subset of features of `push`. In particular, it does not support:
	* application manifests
	* flags to set the stack or modify the default mapped route 
	* exclusions from a `.cfignore` file
* If you are using an application manifest, you cannot include the `buildpack` key or future pushes will not function properly.
* You can use the following commands to update the configuration of an application started with `v3-push`: `map-route`, `bind-service`, `v3-set-env`, `v3-scale`, `v3-set-health-check`. For more information about V3 commands, see the [Using Experimental cf CLI Commands](../devguide/v3-commands.html) topic.

For more information about using the cf CLI, see the [Cloud Foundry Command Line Interface](../cf-cli/index.html) topic.
{'fraction_non_alphanumeric': 0.09798798014110269, 'fraction_numerical': 0.01985889730859681, 'mean_word_length': 4.492109038737446, 'pattern_counts': {'":': 0, '<': 31, '<?xml version=': 0, '>': 31, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3087016', 'n_tokens_mistral': 1173, 'n_tokens_neox': 1096, 'n_words': 487}