Introduction
Understanding organizationsBest practices: organization designUnderstanding componentsManage organizationsManage componentsManage component Jira integrationsOrganization inheritance reference
Understanding users and teamsUnderstanding role-based access controlManage usersManage teamsConfigure role-based access controlRBAC permissions reference
Understanding authentication in CloudBees UnifyPersonal access tokensManage personal access tokensSet up multifactor authenticationConfigure SAML single sign-onConfigure OIDC authenticationConfigure network security policiesNetwork security reference
Understanding platform configurationUnderstanding environmentsManage properties and secretsManage environmentsTrack environment inventoryConfigure containersSet up preconfigured actionsConfigure notificationsSet up Slack webhook notifications
Accessibility policy referenceShared responsibility model referenceSubscription and services agreementSupport policiesSupported browsers and external tools
Introduction
Understanding application security posture managementUnderstanding Jira ticket creationUnderstanding security center workflowsConfigure security toolsConfigure implicit security analysisConfigure Jira ticketing for an applicationConfigure SBOM analysisDefine security SLAsTriage security findingsUse the organization security dashboardUse the component security centerUse the application security centerUse security overview
Get started with security scanningConfigure SAST scanningConfigure DAST scanningConfigure container scanningConfigure SCA scanningConfigure secret scanningConfigure IaC scanningVerify CloudBees action image signatures and SLSA attestationsSecurity scanner referenceSecurity findings taxonomy
Introduction
Actions catalog
Understanding workflowsCreate a build workflowCreate and manage workflowsCreate reusable workflowsTrigger workflows remotely
View pending approval tasks in your inboxMonitor workflow runsView test results in runsView evidence in runsView deployments in runsManage workflow artifacts
Understanding custom actionsCreate a custom action
Configure workflow credentialsConfigure AWS credentialsConfigure container registry credentialsConfigure Git credentialsIntegrate CyberArk Conjur secrets
Check out source codeBuild and publish container imagesTest and validate containers in workflows
Publish test resultsPublish evidence itemsGenerate a software bill of materialsManage ServiceNow change requestsServiceNow actions reference
Workflow syntax referenceJobs syntax referenceSteps syntax referenceServices syntax reference
Introduction
Understanding release orchestrationManage applicationsCreate deployer workflowsCreate staged workflowsCreate and manage releasesOrchestrate multi-workflow releasesRelease management reference
Understanding artifact managementRegister and track artifactsStore and retrieve artifactsPromote artifactsGenerate a software bill of materialsArtifact management reference
Deploy with HelmDeploy to KubernetesContainer deployment reference
Deploy to AWSAWS deployment reference
Deploy with enterprise platformsExecute remote deployment commandsEnterprise deployment reference
Verify deployments with New RelicDeployment verification reference
Introduction
Understanding feature managementUnderstanding Configuration as CodeGet started with feature managementCreate and manage feature flagsConfigure feature flag targetingOrganize feature flagsImplement feature flag governanceEnable secret modeConfiguration as Code reference
Understanding flag impressions and activity statusUnderstanding flag healthUnderstanding code referencesReview and clean up feature flagsSet up code references
Understanding Jira integration for feature flagsSet up the Jira integrationLink Jira tickets to feature flags
Understanding multiple SDK keysBuild your first mobile app with feature flagsBuild your first feature-flagged web applicationBuild your first feature-flagged backend serviceInstall client-side SDKsInstall server-side SDKsConfigure multiple SDK keysFlag implementation reference
Backend SDK referenceGo SDK referenceJava SDK referencePython SDK referenceRuby SDK referencePHP SDK reference.NET/C# (server-side) SDK referenceNode.js SDK referenceMobile SDK referenceAndroid SDK referenceiOS/tvOS SDK referenceObjective-C SDK referenceSwift SDK referenceReact Native SDK referenceWeb SDK referenceJavaScript (browser) SDK referenceJavaScript SSR SDK referenceClient SDK referenceJava client SDK reference.NET/C# (client-side) SDK referenceC (server-side) SDK referenceC++ (server-side) SDK referenceC (client-side) SDK referenceC++ client SDK reference

Diagnose failed runs with the AI Assistant

1 minute read
How-to guide— Task-oriented: directions to achieve a specific goal.

Find out why a workflow run failed without opening the run and searching its logs. Diagnose with AI opens the AI Assistant with that run’s context, so it can explain the likely cause.

Diagnose with AI is available on all failed runs in these lists:

  • Runs

  • Components

  • Releases

  • The Runs tab of a component

Diagnose a failed run

To diagnose a failed run with the AI Assistant:

  1. Navigate to a list that shows workflow runs, such as Runs.

  2. Find the failed run you want to investigate.

  3. Hover over the failure icon.

  4. Select Diagnose with AI.

The AI Assistant opens in the side panel with the failed run’s context and explains the likely cause. You stay on the list, so you can diagnose another failure or open the run for more detail.

To keep the diagnosis separate from other work, select New Chat in the AI Assistant before you select Diagnose with AI.

Follow up on the diagnosis

After the AI Assistant explains the failure, ask follow-up questions in the same chat, for example:

  • How do I fix this?

The diagnosis is saved in Chat History, so you can return to it later.

Manage AI Assistant conversations
AI Assistant capabilities reference