CentOS Pipeline

Run arbitrary shell commands on CentOS environments using the Command Line tool. Supports input/output parameters, tagged dependencies, and custom output file capture.Command LineShell scriptsCentOS

Prerequisites

• Opsera account with pipeline creation permissions

• Command Line tool registered and connected in Opsera

• SCM repository with scripts/project registered in Tool Registry

Pipeline setup

1

Create the pipeline step

Log in → Pipeline → create or open pipeline. Step Setup: enter step name, Tool = Command Line. Save.

2

Configure step settings

Select Tool, Job, Account, Repository, and Branch. Enter commands one per line in the Commands field.

Field	Description
Commands	Shell commands, one per line — executed sequentially
Input Parameters	Parameters passed into command execution as environment variables
Output Parameters	Select parameters and define Output Path and File Name
Dependencies	Tagged dependency versions selected from dropdown

3

Run and view logs

Click Start Pipeline. Open pipeline → Summary tab → Pipeline Logs → Console Output.

Points to remember

• Commands are executed sequentially in the order entered — a non-zero exit code from any command halts the pipeline at that step.

• Use Input Parameters to inject sensitive values (tokens, credentials) rather than hardcoding them in the Commands field — this ensures they are masked in logs.

• Define Output Path and Output File Name to capture build artifacts from the command execution for use in downstream pipeline steps.

• Use the Dependencies dropdown to pin specific tool versions (e.g. Java, Node) that your commands depend on — this prevents environment inconsistencies across runs.