Component Reference¶

Complete reference documentation for all RADIUSS Shared CI components.

Component Overview¶

RADIUSS Shared CI provides 9 reusable components organized into four categories:

Core Orchestration:

base-pipeline - Required for all pipelines

Machine-Specific:

Machine Pipelines - Build/test on LC machines (5 components)

Performance Testing:

performance-pipeline - Benchmarking and GitHub reporting

Utilities:

Utility Components - Draft PR filter, branch skip (2 components)

How to Use This Reference¶

Each component page includes:

Purpose - What the component does and when to use it
Inputs - Complete table of all inputs (required/optional)
Exported Templates - Job templates you can extend
Variables - Environment variables set by the component
Examples - Working code snippets
Common Issues - Troubleshooting tips

Quick Input Reference¶

Common Inputs Across Components¶

Many components share these inputs:

Input	Type	Used By
`github_project_name`	string	base-pipeline, all machine pipelines, utilities
`github_project_org`	string	base-pipeline, all machine pipelines, utilities
`github_token`	string	base-pipeline, utilities, performance-pipeline
`job_cmd`	string	All machine pipelines, performance-pipeline
`llnl_service_user`	string	All machine pipelines

See individual component pages for complete input specifications.

Version Compatibility¶

All components in a pipeline should use the same version:

# Good: All @v2026.02.2
include:
  - component: .../base-pipeline@v2026.02.2
  - component: .../dane-pipeline@v2026.02.2
  - component: .../utility-draft-pr-filter@v2026.02.2

# Bad: Mixed versions
include:
  - component: .../base-pipeline@v2026.02.2
  - component: .../dane-pipeline@v2025.12.0  # Don't mix!

Reason: Components share template names and variable conventions. Mixing versions can cause template conflicts or missing definitions.