Sandboxes
A sandbox gives a task its own code working copy and verification environment. A pipeline can prepare it, or you can start one manually.
Available actions
- View previews and distinguish manual environments from pipeline environments.
- Start a manual preview from a project profile without a route task.
- Inspect preparation progress, results and logs.
- Open frontend and API ports.
- Copy working copy paths and branch names.
- Run profile-declared actions and remove manual environments.
Environment preparation
The profile prepares working copies, dependencies, services and data. Profiles using containers require configured Docker. Separate previews still require project setup.
Manual previews use a task number or an available service number. Ports and slots are allocated alongside the pipeline to avoid resource collisions.
Lifecycle ownership
Manage active-attempt previews from the pipeline task card. External shared environments do not become sandboxes and are not removed here. Manual teardown distinguishes ordinary removal from removal with uncommitted changes.
Related tools: code, terminal, Docker and databases.
Pipelines can also use a prepared shared working copy with one active attempt at a time.