CLI CI/CD & Environment Promotion

The current CLI command set works well for CI/CD. unmeshed login can run non-interactively.

Use one of these patterns in CI/CD:

Use --non-interactive when you want the pipeline to fail immediately if required login inputs are missing.

For most deployments, the core commands are:

Those commands bulk upsert JSON or YAML files from a file path or a directory.

If your definitions depend on scripts, templates, or payload files stored on the server, upload them first:

Then apply the matching definitions:

process download-definition is the most direct way to export a definition from one environment into a file that another environment can import.

Example on Linux or macOS using separate home directories:

That pattern works because each HOME points the CLI at a different ~/.unmeshed.ini.

Schedules are typically promoted from version-controlled files rather than by downloading them from the server. Keep schedule definitions in your deployment artifact, then push them to the target environment with:

One common sequence is:

1. Build and validate your definition and schedule artifacts
2. Upload supporting files with unmeshed upload
3. Apply process definitions with unmeshed update pd
4. Apply schedules with unmeshed update sch
5. Run smoke checks with unmeshed run, unmeshed call, or unmeshed search

• Definitions & File Ops
• Servers & Credentials
• Run, Search, & Steps