> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/cli/release/builds/create.md).

# release builds create

Command reference doc for the Release CLI

Creates a new build for the given branch or tag

## Description

If the --wait flag is passed, the command will exit with a non-zero exit code if the build fails.

Only one of --branch or --tag can be specified. If neither is specified, the repository default branch is used.

Any environments configured to auto-deploy that are tracking the build's branch or tag will be deployed when the build completes.

```
release builds create [flags]
```

## Examples

```

Trigger a build asynchronously:
> release builds create --app backend --branch feature-1234

Wait until the build is completed before exiting and include log output:
> release builds create --app backend --branch feature --wait --verbose

Get build details as JSON:
> release builds create --app backend --wait --verbose -o json > results.json
```

## Options

| `--account <string>`      | Account name or ID (default: $RELEASE\_ACCOUNT or "account" in config file) |
| ------------------------- | --------------------------------------------------------------------------- |
| `--app <string>`          | App name or ID (default: $RELEASE\_APP or "app" in config file)             |
| `--branch <string>`       | Branch to build                                                             |
| `-o`, `--output <string>` | Set the output format (table \| json \| json-pretty)                        |
| `--tag <string>`          | Tag to build                                                                |
| `--verbose`               | Verbose log output                                                          |
| `--wait`                  | Wait for build to complete before exiting                                   |

## Options inherited from parent commands

| `--config <string>` | config file (default is $HOME/.release.yaml) |
| ------------------- | -------------------------------------------- |
| `--debug`           | enable debug logging                         |

## Related

* [release builds](/cli/release/builds.md) - Manage builds


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.release.com/cli/release/builds/create.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.