Power Ci Invoker

Trigger and manage CI pipeline runs with intelligent job selection and parallel execution controls.

When to Use This Command

Run this command when you need to:

• Trigger specific CI pipeline jobs or stages from your terminal without navigating the CI platform UI
• Re-run failed CI jobs with modified parameters or environment overrides
• Orchestrate multiple CI pipelines across repositories or branches in a single invocation

Consider alternatives when:

• You need to set up a new CI pipeline from scratch (use ci-setup-rapid instead)
• Your CI system requires interactive browser-based authentication that cannot be handled via CLI tokens

Quick Start

Configuration

Copy
name: power-ci-invoker
type: command
category: automation

Example Invocation

Copy
claude command:run power-ci-invoker --pipeline build-test --branch feature/auth --jobs lint,test,build

Example Output

[CI Invoker] Authenticating with CI platform... OK
[CI Invoker] Pipeline: build-test | Branch: feature/auth
[Trigger] Job 'lint' queued (#4521) .......... PASSED (42s)
[Trigger] Job 'test' queued (#4522) .......... PASSED (1m 38s)
[Trigger] Job 'build' queued (#4523) ......... PASSED (2m 12s)
[Summary] 3/3 jobs passed | Total: 4m 32s
[Artifacts] Build output available at: /tmp/ci-artifacts/4523/

Core Concepts

CI Invocation Overview

Aspect	Details
Supported Platforms	GitHub Actions, GitLab CI, Jenkins, CircleCI, Azure Pipelines
Auth Methods	API tokens, SSH keys, OAuth via environment variables
Job Selection	Filter by name, stage, tag, or dependency graph position
Output Modes	Streaming logs, summary-only, or JSON for scripting

Invocation Workflow

[User Command]
      |
[Authenticate] --> API token / SSH key
      |
[Resolve Pipeline] --> Branch + commit
      |
[Select Jobs] --> Filter by name/stage
      |
[Trigger + Poll] --> Stream logs
      |
[Collect Results] --> Artifacts + status

Configuration

Parameter	Type	Default	Description
pipeline	string	required	Name or ID of the CI pipeline to trigger
branch	string	current	Git branch to run the pipeline against
jobs	string	all	Comma-separated list of specific jobs to run
wait	boolean	true	Block until all jobs complete and return exit code
env-override	string	none	KEY=VALUE pairs to inject into the CI environment

Best Practices

1. Use Selective Job Targeting - Invoke only the jobs you need rather than the full pipeline. This reduces CI minutes consumed and provides faster feedback during iterative development.

2. Cache Authentication Tokens - Store CI platform tokens in environment variables or a secure credential store. Avoid re-authenticating on every invocation to minimize latency.

3. Stream Logs for Debugging - Enable log streaming mode when diagnosing failures so you see output in real time rather than waiting for the entire job to complete before reviewing.

4. Set Timeouts on Long Pipelines - Always specify a --timeout value for pipelines that might hang. This prevents the command from blocking your terminal indefinitely on stuck jobs.

5. Combine with Git Hooks - Wire the invoker into pre-push hooks to automatically validate critical CI jobs before code reaches the remote, catching failures before they affect the team.

Common Issues

1. Authentication Token Expired - CI platform tokens have expiration dates. Regenerate your token from the platform settings and update the CI_TOKEN environment variable.

2. Pipeline Not Found on Branch - The specified pipeline configuration must exist on the target branch. Ensure the CI config file is committed to that branch before invoking.

3. Rate Limiting on Rapid Invocations - CI platforms throttle API calls. Add a brief delay between batch invocations or use the --batch flag to group multiple triggers into one API request.