# Quickbuild

Build artifact(s) of your packages in the current project without dependency validation for unlocked packages

* [`sfp quickbuild`](#sfp-quickbuild)

## `sfp quickbuild`

Build artifact(s) of your packages in the current project without dependency validation for unlocked packages

```
USAGE
  $ sfp quickbuild -v <value> --branch <value> [--json] [--loglevel
    trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL] [--repository <value>] [-e <value>] [-t
    <value>] [--sfp-server-url <value>] [--apiversion <value>] [--diffcheck] [-p <value>...] [-r <value>] [-c <value>]
    [-f <value>] [--artifactdir <value>] [--waittime <value>] [--buildnumber <value>] [--executorcount <value>] [--tag
    <value>] [--releaseconfig <value>...]

FLAGS
  -c, --commit=<value>
  -e, --email=<value>              [env: SFP_SERVER_USER] Email address for authenticated user. Ignored if
                                   --application-token is provided.
  -f, --configfilepath=<value>     [default: config/project-scratch-def.json] Path in the current project directory
                                   containing  config file for the packaging org
  -p, --buildOnly=<value>...       Only build artifacts for the provided package names,use comma separated list of
                                   package names if there are multiple packages
  -r, --repourl=<value>            Custom source repository URL to use in artifact metadata, overrides origin URL
                                   defined in git config
  -t, --application-token=<value>  [env: SFP_SERVER_TOKEN] Application token for CI/CD authentication. Takes precedence
                                   over --email.
  -v, --devhubalias=<value>        (required) Username or alias of the Dev Hub org.
      --apiversion=<value>         Override the api version used for api requests made by this command
      --artifactdir=<value>        [default: artifacts] The directory where the generated artifact is to be written
      --branch=<value>             (required) [default: main] The git branch that this build is triggered on, Useful for
                                   metrics and general identification purposes
      --buildnumber=<value>        [default: 1] The build number to be used for source packages, Unlocked Packages will
                                   be assigned the buildnumber from Salesforce directly if using .NEXT
      --diffcheck                  Only build the packages which have changed by analyzing previous tags
      --executorcount=<value>      [default: 5] Number of parallel package task schedulors
      --loglevel=<option>          [default: info] logging level for this command invocation
                                   <options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
      --releaseconfig=<value>...   Path to the release config file(s) to limit packages built by domains
      --repository=<value>         The repository identifier. E.g `owner/repo`
      --sfp-server-url=<value>     [env: SFP_SERVER_URL] URL of the SFP server. Can be set via environment variable
                                   `SFP_SERVER_URL` or config: sfp config:set server-url
      --tag=<value>                Tag the build with a label, useful to identify in metrics
      --waittime=<value>           [default: 120] Wait time for command to finish in minutes

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Build artifact(s) of your packages in the current project without dependency validation for unlocked packages

ALIASES
  $ sfp orchestrator quickbuild
```

*See code:* [*src/commands/quickbuild.ts*](https://source.flxbl.io/flxbl/sfp-pro)


---

# 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://docs.flxbl.io/flxbl/sfp/sfp-community/cli-reference-v50-and-below/core/quickbuild.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.