C3 AI Documentation Home

C3 AI Studio Release Branches

Release Management > Branches in C3 AI Studio links your application's source control repository to the C3 Agentic AI platform. It displays branch statuses and recent build results, and allows you to review or initiate builds. Each listed branch represents a separate line of development or release, and supports parallel feature development, hotfixes, and production-ready deployments.

To learn how to link repository branches to your C3 AI Studio application, see Register and Delete a Group of Branches in C3 AI Release Management.

View and manage branches

The Release Management > Branches page in C3 AI Studio displays a list of all repository branches linked to your application. Filter branches by entering part of a branch name in the search field.

The list contains the following columns:

  • Branch: Repository branch name (for example, main, feature/new-feature). Select this link to open its Branch detail page.
  • Branch group: Pattern-matched group, as defined by administrators (for example, branches matching feature/*).
  • Repository: Canonical repository name.
  • Last Build Status: Result of the most recent build. Statuses include Aborted, Error, Success, or Test failures.
  • Last Success: How long ago since the branch was successfully built.
  • Last Failure: How long ago since the branch encountered a build failure.
  • Last Duration: Time taken for the most recent automation attempt, including tests and build.

Branch controls

Hover over branch list items to reveal additional icon controls at the end of the row:

  • External Link icon (a square containing a diagonal arrow): Navigate directly to the branch in the source repository.
  • Play icon: Manually trigger a new build for the branch.
  • Ellipsis icon (...): Opens an action menu where you can deactivate the branch. Deactivated branches do not trigger builds.

Branch detail

The Branch detail page contains:

  • Page header: Displays the branch name and includes the following controls:
    • Trigger build: Start a new build manually.
    • External Link icon: Go to the source repository.
    • Hammer icon: Start a build with custom configuration values (for example, external API keys).
    • Stop icon: Deactivate the branch. Deactivated branches do not trigger builds.
  • Graphs:
    • Branch history graph: Visualizes recent builds, color-coded by outcome (red for failure, green for success). X-axis: build number; Y-axis: number of tests run.
    • Build duration graph: Shows duration and outcome of each build attempt.
  • All builds list: A detailed history of builds for the active branch. The columns show the following information about each build:
    • Build order
    • Status
    • Test results
    • Build duration
    • Start time
    • Server version
    • Commit hash (linked)

Inspect a build in detail

Select a build number from the All builds list to access the Build detail page. The page header summarizes:

  • Branch: Source branch name.
  • SHA: Commit hash, linked to the source repository.
  • Coverage report: Download test coverage results.
  • Server version: Target C3 Agentic AI Platform version.
  • Total machine time: Compute time used for the build.

The build detail page includes three tabs:

Overview

The Overview tab provides a high-level summary of the build. This section's header displays the following:

  • Build Results: Total, failed, skipped, and passed test counts for this build.
  • Build Duration: Time to run the build, including tests and artifact generation.
  • Show Graphs: Option to display graphs for both Build Results and Build Duration.

Pipeline

The Pipeline tab shows the branch's build steps in a visual flowchart. You can use it to identify failing steps within the build process, or steps that take the longest time to resolve. Each step shows:

  • The step's name and an icon indicating success or failure.
  • The total time spent running the step.
  • Number of retries before success. Shown only for steps that initially failed.

Select a step to access logs, errors, and executor details for that step. Use this information to troubleshoot issues that may arise in a step.

Config

The Build Config tab shows build settings that define behavior and conditions during the branch's build process. The tab contains a Build Secret table with any API or SDK keys for the branch, and a Build Config list with the following values:

  • buildDocIndex: If true, generates an index for documentation in the resulting build artifact.

  • devBundleTimeout: Stop compiling development UI bundles after this period of inactivity (minutes). Not used when shouldGenerateDevBundles is false.

  • disableCodeAnalysis: If true, disables code analysis for the branch.

  • enableC3UiCoverage: If true, enables testing for UI components.

  • enableJepCoverage: If true, enables code coverage for Java Embedded Python (JEP) files.

  • enableJsServerCoverage: If true, enables code coverage for JavaScript files.

  • enablePythonCoverage: If true, enables code coverage for Python files.

  • failIfPkgIssues: If true, the build stops when a compilation error occurs.

  • maxTestDuration: Abort testing if it exceeds this duration (minutes).

  • pkgsToExclude: An optional list of dependencies to exclude when building the application from the current branch.

  • pkgsToInclude: An optional list of dependencies to include when building the application from the current branch.

  • prodBundleTimeout: Stops compiling production UI bundles after this many minutes of inactivity. Ignored if shouldGenerateProdBundles is false.

  • registerArtifactsUpstream: Register artifacts to Artifacts Hub when a build is successful.

  • reportResultsToCodeAnalytics: If true, record code analysis results.

  • restartAppOnFailure: Restart the application when a build is unsuccessful.

  • restartExecutorBetweenSteps: If true, the build restarts an executor after it completes a step and before it picks up another, regardless of the step's status.

  • allowBuildWithUnsafeServerVersion: If true, allows builds to run on executors with newer server versions. Not forward-compatible: use only for version previews.

    An Executor is a transient C3 AI server spawned to run a build step. This approach can speed up the build but may lead to less stable behavior.

  • restartExecutorOnError: If true, restarts the step executor when an error occurs, even if restartExecutorBetweenSteps is false.

  • shouldGenerateDevBundles: If true, generates UI bundles for a development application.

  • shouldGenerateProdBundles: If true, generates UI bundles for a production application.

  • skipPkgIssues: If true, the build ignores any errors encountered while bundling package dependencies.

  • testStrategies: Any test strategies specified by the administrator.

See also

Was this page helpful?