Batch Build & Automation

Automate every build.
Ship on schedule.

Command-line switches, text-based directives, and proper exit codes let you plug Paquet Builder into any CI/CD pipeline. Build x86, x64, and ARM64 installers from a single project — hands-free.

Free Download Read the docs

Paquet Builder command-line compiler usage and switches

Feature Tour7 / 11

Batch Build & Automation

All Features

Command-Line Interface

One command. Every platform.

Extensive command-line options automate Self-Extracting package creation from the GUI or the dedicated console compiler — ideal for build machines without Windows user login.

build.bat

PBUILDER.EXE "C:\My Documents\pbtest\testdirect1.pbpx" /exetype:1 /c /q /s /filelistupt

/q /s silent build /exetype x86 / x64 / ARM64 /filelistupt wildcard refresh /arcfile 7z → installer

Structured exit codes. Both the GUI and console compilers return proper exit codes on every build — plug PBUILDER.EXE into any CI/CD pipeline and branch on success, warning, or failure.

How text directives work in Paquet Builder — transform projects, update files, and create packages from .ini-style configuration

release.pbd

# Update version info, then build x64
[Project]
Source=C:\build\myapp.pbpx
ExeType=1

[VersionInfo]
FileVersion=2026.1.0.0
ProductVersion=2026.1.0.0

[Build]
Compile=1

Text-Based Directives

Script your packages like config files

Use directive files to customize Self-Extracting packages, update source files, modify version information, and more. Directives are text-based and resemble traditional .ini configuration files — simple to read, easy to version-control.

Transform existing projects: Override settings, swap files, and update metadata without opening the IDE.
Create projects from scratch: Define a complete package in a directive file — no prior .pbpx required.
CLI or App menu: Pass directives via command-line or the App menu — your choice.
Console compiler support: The console compiler fully supports directives for streamlined CI/CD automation.

Headless CI/CD

Runner-friendly builds

GitHub Actions, Azure DevOps, Jenkins — any Windows runner that doesn't have an interactive desktop session needs the dedicated console compiler (PBCMDCOMPILER.EXE). Same flags, same directives — no GUI session required.

No logon required: The console compiler runs without an interactive Windows session — ideal for build agents.
Branch on exit code: Zero = success, non-zero = fail. Standard Windows process semantics — no parsing needed.
Upload artifacts: Pass the output .exe to your favorite artifact or release action.

Learn about the console compiler

.github/workflows/release.yml

name: Build installer
on:
  push:
    tags: ['v*']

jobs:
  build:
    runs-on: windows-latest
    steps:
      - uses: actions/checkout@v4

      # Console compiler — no GUI session needed
      - name: Build x64 installer
        run: |
          "C:\Program Files\Paquet Builder\PBCMDCOMPILER.EXE" `
            "${{ github.workspace }}\myapp.pbpx" `
            /exetype:1 /c /q /s /filelistupt

      - uses: actions/upload-artifact@v4
        with:
          name: installer
          path: output/*.exe

Keep Touring

Move through the feature set without jumping back to the grid

Use the pager to continue the product tour, or jump back to the full overview at any point.

Previous Feature

Multilanguage

Ship installers that speak your users' language. 11 built-in languages with full Unicode support and automatic locale detection.

Overview

See all features

Next Feature

MCP Server

Control Paquet Builder from Claude Code, Cursor, or Windsurf via the Model Context Protocol. 20+ tools, fully headless.

Ship builds on autopilot

Silent builds. Structured exit codes. CI/CD ready.

Free Download

Automate every build. Ship on schedule.