# How-to guides overview

> How-to guides are **task-oriented walkthroughs**: you have a specific outcome in mind, the page shows the exact commands to get there. Unlike [Concepts](./concepts-overview.md) (which explain how the CLI is organized) and the [Command reference](./command-reference.md) (which lists every flag), how-tos start from a real goal and end with a working pipeline you can copy.

How-to guides are **task-oriented walkthroughs**: you have a specific outcome in mind, the page shows the exact commands to get there. Unlike [Concepts](./concepts-overview.md) (which explain how the CLI is organized) and the [Command reference](./command-reference.md) (which lists every flag), how-tos start from a real goal and end with a working pipeline you can copy.

For platform-specific complete pipelines (Azure DevOps, GitHub Actions, Jenkins, GitLab CI), see [CI/CD recipes](./recipes-azure-devops.md) — the section right below this one in the sidebar.

## The five how-tos

| Page | Goal | Tools used |
|---|---|---|
| [Pack and publish a Solution](./howto-pack-publish-solution.md) | Versioning discipline, multi-environment promotion, rollback. The full Solution lifecycle from a working laptop. | `uip solution pack / publish / deploy` |
| [Deploy to Orchestrator from CI](./howto-deploy-from-ci.md) | The platform-agnostic principles behind every CI recipe: auth, caching, tool pre-install, version pinning. | `uip login`, `uip tools install`, `uip solution …` |
| [Run tests in a pipeline](./howto-run-tests.md) | The launch → wait → verify pattern for Test Manager. Why a single command is not enough to fail a build on red tests. | `uip tm testsets run / wait / report get` |
| [Deploy an Agent](./howto-deploy-agent.md) | Full agent lifecycle: scaffold, validate, pack, publish, deploy. Contrast with Solution-based deployment. | `uip agent init / validate / pack / publish / deploy / run` |
| [Manage Orchestrator assets and queues](./howto-manage-resources.md) | Bulk-deploy assets from CSV, upload bucket files, dispatch queue work, manage triggers and webhooks. | `uip resource …` |

## Where to start

**New to the CLI?** Read [Quickstart](./quickstart.md) and [Your first pipeline](./first-pipeline.md) first — both are in [Get started](./installing-uipath-cli.md). They give you the basic command shapes the how-tos build on.

**Shipping a Solution end-to-end?** Read in this order:

1. **Pack and publish a Solution** — versioning + multi-tenant promotion.
2. **Deploy to Orchestrator from CI** — the principles you'll apply in your platform's recipe.
3. **Run tests in a pipeline** — wire the launch-wait-verify chain into the deploy.
4. Pick a [CI/CD recipe](./recipes-azure-devops.md).

**Working with Agents?** [Deploy an Agent](./howto-deploy-agent.md) is the standalone path. Skip Solution packaging unless your agent ships alongside RPA workflows.

**Managing live tenant resources outside a Solution?** [Manage Orchestrator assets and queues](./howto-manage-resources.md) is the catalog of `uip resource` patterns.

## What's *not* in How-to guides

- **First-time setup.** That's [Installing UiPath CLI](./installing-uipath-cli.md).
- **The why** behind a command. That's [Concepts](./concepts-overview.md) and individual reference pages.
- **Per-platform YAML/Groovy.** That's [CI/CD recipes](./recipes-azure-devops.md).
- **Per-flag detail.** That's [Command reference](./command-reference.md).

## See also

- [Scripting patterns](./scripting-patterns.md) — generic shell techniques every how-to assumes.
- [Authentication](./authentication.md) — the auth flows the how-tos use as a starting point.
- [CI/CD recipes](./recipes-azure-devops.md) — copy-pasteable pipelines per platform.