# Build
The `build` command provides the ability to build either a complete or incremental deployment, which can then be deployed to a target JADE database.
## Revisions
The [revision string](https://git-scm.com/docs/git-rev-parse.html#_specifying_revisions) may refer to a single commit, in which case a complete deployment will be built.
```bash
jadegit build HEAD mul C:\temp\build
```
It may also refer to a [range of commits](https://git-scm.com/docs/git-rev-parse.html#_specifying_ranges), in which case an incremental deployment will be built, including any commands required to rename, delete, move classes, and any other special operations needed to upgrade schemas from the prior version.
```bash
jadegit build v0.1..v0.2 mul C:\temp\build
```
## Formats
The deployment format of the build is specified via a subcommand.
### Multiple Schema File Extract
The `mul` subcommand provides the ability to build a standard [multiple schema file extract](https://secure.jadeworld.com/JADETech/JADE2022/OnlineDocumentation/#resources/userguide/ch10schemaextractload/multiple_schema_file_syntax.htm).
The destination output directory is required, and an optional name may be specified which defines the name of the \*.mul file created.
```powershell
jadegit build v0.1..v0.2 mul -n "v0.2 Update" C:\temp\build
```
{% hint style="warning" %}
Due to JADE limitations, this format does not support the use of command files (needed to handle renames and other special operations). Other deployment formats (to be implemented) will support command files.
{% endhint %}
### Scripted Deployment
The `pwsh` subcommand provides the ability to build a scripted deployment using PowerShell.
Use the following command to run the deployment from the output directory (copying to host of the target database beforehand if required).
```powershell
.\deploy.ps1 -bin "C:\Jade\bin" -path "C:\Jade\system" -ini "C:\Jade\jade.ini"
```
### Generic XML Format
The `xml` subcommand provides the ability to build a generic deployment, with an XML instruction file intended to be transformed/processed as needed by third parties to handle deploying/publishing updates in a customized manner.
