A CI step with a verifiable result
Deliver a folder from a pipeline and let the exit code decide whether the next step may run.
You need
The pipeit CLI (Linux, macOS, Windows), signed in, and the rights each command needs. A one-time device sign-in and receive setup already done.
A job can use the normal CLI. Example of a plain folder delivery:
pipeit send ./dist --contents --profile v2 --mode inbox \
--target TARGET-DEVICE --destination project --timeout 20m --jsonThe job must adopt the exit code. JSON output can contain IDs and private names; keep only the cleaned diagnostic data you need in the build system. Do not store the login URL, tokens or keys as build artifacts. CI needs a protected state of its own and must find the prepared job again when resuming.
| Result | Meaning for the job |
|---|---|
Exit 0 on send | Verified receipt; no automatic application start |
| Exit 1 | Error or interruption; check the code and the retry hint |
| Exit 2 | Wrong call or prerequisites |
| Exit 3 | Signed receiver block, for example a storage problem; the target side may have to act |
| Exit 4 | Time limit; keep the existing transfer ID and resume deliberately |
| Exit 5 on a matching action | Activation or management action still pending, no completion receipt yet |
| Exit 6 on maintenance | Cleanup pending; a delivery that was already confirmed has not failed retroactively |
Scroll sideways to see the whole table.
To resume, use transfer resume TRANSFER-ID, or group stream resume REQUEST-ID for groups. A new send is a new job. For folders, build artifacts must not be changed or cleaned up in the meantime.
Related guides
- Command line and servers
Sender A: choose the destination and send a file
Pick the receiver’s alias and send a large file with a receipt you can rely on.
- Command line and servers
Example: deliver the contents of a website
Send a build as a prepared state and switch to it deliberately afterwards.
- Command line and servers
Status, progress and resuming
Read the state of a transfer and continue the same job instead of starting a new one.
Still stuck?
Check the troubleshooting guide first. If that does not help, tell us what happened.