| Status | ||||
|---|---|---|---|---|
|
| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Manage the PIPEFORCE Cloud remotely
Connect On Premises systems with PIPEFORCE Cloud
Easily excecute execute single cloud commands or pipelines on the terminal
Develop integrations, apps, workflows and reports from within your preferred IDE
Run and monitor tests
Automate and execute business workflows
...
The tutorial Setup local workspace + CLI shows, how to install and work with the CLI.
Download & Installation
See the Downloads section on how to install this tool.
Usage
The main structure of a CLI command is always like this:
| Code Block |
|---|
pi <action> <args> |
To get a list of all supported actions and their parameters, use the help command:
...
Below, you can find the description of the most important actions and their usage. For a full list and detailed explaination of its options, use pi help.
pi command
This executes a single pipeline command at the server-side and returns the result.
...
Even if you have a different favorite editor, we recommend you to start with this one, since it is easier to follow all of the examples. Later, you can switch to a different editor if you want.
...
After you have installed the CLI and setup an a PIPEFORCE instance, you can create a local workspace. Inside this workspace you can store all resources which must be deployed later to PIPEFORCE.
...
If you open this file, you can see it containing contains a simple hello world demo pipeline, which logs “Hello World” into the server log, and writes it into the body.
...
After the command was executed, you can see that your pipeline has been successfully created uploaded into the property store.
Anytime you change a resource in the workspace, calling pi publish afterwards, will create or update only those resources which have been changed after the last publish. This way, you can work in a very effective way.