cloudbees-oss

Generate a CI health report for a component or the entire organization. Uses controller analytics, run history, and security posture.

Create a Jira ticket from a build failure, security finding, or improvement recommendation.

Manage feature flags — list, inspect, enable, disable, or create flags. Supports progressive rollout workflows.

Show a unified view of all CI/CD pipelines across Jenkins, GitHub Actions, and CloudBees Workflows. The cross-tool picture no single tool can provide.

Check release readiness across all components. Verifies CI status, security gates, and feature flag states for a go/no-go decision.

Analyze security posture across components. Shows vulnerabilities by severity, scanner type, SLA status, and remediation priority.

Analyze the latest failed CI run for a component. Identifies failing jobs and steps, reads logs, determines root cause, and classifies the failure.

Assess whether a target project directory is a good candidate for CloudBees Smart Tests based on CI configuration and recent CI behavior. Use when a user asks whether Smart Tests is likely to help, whether a repository or directory is suitable for Smart Tests adoption, or asks to evaluate CI duration, flaky test reruns, rerun frequency, GitHub Actions, AWS CodeBuild, Jenkins, buildspec, Jenkinsfile, or workflow evidence for Smart Tests value.

Tap into the product knowledge of CloudBees Smart Tests to reliably answer users questions.

Onboard a GitHub repository to CloudBees Unify by creating one or more components and triggering a security scan. Use when the user says things like "onboard this repo to Unify", "add this project to CloudBees Unify", "register this repo in Unify", "create a Unify component for this repo", "set up this repo in CloudBees", or "connect my repo and run a security scan".

List CloudBees Unify components in an organization. Use when the user asks "what components do I have", "list services", or needs to look up a component name/ID before another operation.