# EXEC - Deploy components

```batch
bc DEPLOY EXEC/c <ComponentID> /dstEnv=01-DEV
```

Deploy or promote your components to an [environment](https://github.com/SchmidteServices/Boomi.Commands/blob/dev/doc/commands/deploy/deploy-info/broken-reference/README.md).

{% content-ref url="/pages/s3PPaHS4lClCDXA2jNBL" %}
[DEPLOY EXEC Arguments](/boomi-console/commands/arguments/deploy-arguments/deploy-exec-arguments.md)
{% endcontent-ref %}

{% hint style="info" %}
**Deploy or Promote**

A **Deployment** takes place\
when a component is **packaged and deployed**

* from Repository to an environment (usually to DEV).

We call it a **Promotion** when

* a packaged component is 'deployed'\
  from one Environment to another.

Typically, you deploy from Repository to `DEV` environment\
and you promote your packaged components from `DEV` to `TEST`.
{% endhint %}

To perform a deployment, you need to specify one or more component(s) which will be packaged first, before it is deployed to the destination environment.

Optionally, you can specify a `/DeploymentNote` and or a `/PackagedComponentNote`.

You cannot yet specify a version because this is set automatically to `{Date}-{User}.{seqNo:2}`.

### Deployment

Each component that is [resolved using the command-line arguments](/boomi-console/commands/arguments/common-arguments.md#componentsources) a new packaged component is created. All packaged components in a single deployment get the same version number.

<figure><img src="https://github.com/MarkusSchmidtPro/MSPro.Boomi.Console/blob/main/doc/commands/deploy/deploy-info/broken-reference" alt=""><figcaption><p>Three (packaged) components in one deployment - with the same version number</p></figcaption></figure>

### Promotion

A promotion copies deployed (packaged) component(s) from one environment `/SrcEnv` to another `/DstEnv`. To execute a promotion you refer to the component Ids (not the packaged component ids). *Boomi Console* automatically gets the required packaged component ids from the source environment to copy them to the target.

### Using Sets

The real power of this command comes with the [`/set`](/boomi-console/library/packages.md) option. This allows you deploy / promote many components (a Component Package) in a single run! This will save you a lot of time and it makes your deployments reproducible!

1. [Deploy a Component](/boomi-console/commands/deploy/deploy-info/deployment-from-repos.md) from Repository to an Environment
2. [Promote a component ](/boomi-console/commands/deploy/deploy-info/promotion-to-env.md)from one Environment to the next

Please not,ice, the `DEPLOY EXEC` command refers to the [Environments ](https://github.com/SchmidteServices/Boomi.Commands/blob/dev/doc/commands/deploy/deploy-info/broken-reference/README.md)you have specified in your [project configuration](https://github.com/MarkusSchmidtPro/MSPro.Boomi.Console/blob/main/doc/commands/deploy/deploy-info/broken-reference/README.md). All deployments or promotions are logged in the `Logs` directory on a daily basis for later reference.

![](/files/JDoJbrKBaRhB5kQ8jqjn)

After each deployment or promotion you may use `DEPLOY INFO` to document your deployment state for later evidence.

```
bc deploy info --componentid <YourCompId> 
```

![](/files/gB0O6MoLQz7gCwXUDVVO)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://boomi.markusschmidt.pro/boomi-console/commands/deploy/deploy-info.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.