> For the complete documentation index, see [llms.txt](https://jadelab.gitbook.io/jadegit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jadelab.gitbook.io/jadegit/0.11.1/console/build.md).

# 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.

<figure><img src="/files/EPdAK173pbHpptf2ZvRg" alt=""><figcaption></figcaption></figure>

## 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).

<figure><img src="/files/UpjubvhI7HVSwJc9ZwHJ" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="/files/AfQwxMpWX3e7AUE9sO8N" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="/files/fWT7uOAwUBIhetma3xjk" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://jadelab.gitbook.io/jadegit/0.11.1/console/build.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.
