Problem
In the Portal UI, triggering a build is a single "Build" button on the project page — the UI automatically resolves which pipeline to run and populates all required parameters and labels.
In the CLI, there is no equivalent. The user must:
- Discover the correct build pipeline name (by inspecting previous runs or knowing the naming convention)
- Determine what parameters that pipeline expects and what values to pass
- Attach the correct labels so the run is associated with the project
This means there is no simple CLI equivalent to the Portal's one-click build.
Proposal
Add a high-level command like:
krci project build [--branch main]
This command should:
- Resolve the build pipeline and its required params automatically (the same way the Portal UI does)
- Support
--dry-run to preview the PipelineRun manifest before creating it
- Support
-o json for scripting/agent workflows
Current workaround
krci pipelinerun start <pipeline> --param ... --label ... — requires the user to manually find the pipeline name, figure out the params, and construct a long command to replicate what the UI does in one click.
Problem
In the Portal UI, triggering a build is a single "Build" button on the project page — the UI automatically resolves which pipeline to run and populates all required parameters and labels.
In the CLI, there is no equivalent. The user must:
This means there is no simple CLI equivalent to the Portal's one-click build.
Proposal
Add a high-level command like:
krci project build [--branch main]
This command should:
--dry-runto preview the PipelineRun manifest before creating it-o jsonfor scripting/agent workflowsCurrent workaround
krci pipelinerun start <pipeline> --param ... --label ...— requires the user to manually find the pipeline name, figure out the params, and construct a long command to replicate what the UI does in one click.