Release Management Built-in Roles
C3 AI provides the following predefined roles with permissions to perform release management tasks
C3.JarvisAdminC3.JarvisUser
Assign these roles to users who are responsible for release management tasks.
Release management admin
The typical persona for a user with the C3.JarvisAdmin role is a developer operations engineer or platform administrator. They manage and troubleshoot CI/CD pipelines and manage infrastructure for build configurations.
Release management admin permissions
The C3.JarvisAdmin role has the following capabilities:
Manage builds
- Create, read, update, delete builds.
- Have access to build results, such as logs, statuses, artifacts.
- Manage build configurations.
- Trigger builds and manage build schedules.
- Have access to build content, such as source code and artifacts.
Manage executors
- Manage executors and monitor executor status.
- Control scaling and allocation for executor pools.
Manage branch and repository settings
- Configure branch groups to organize branches for builds.
- Modify branch group configurations.
- Manage Git repositories.
- Configure Git repository settings.
Manage release management operations, settings, and data
- Modify release management configuration settings.
- Clean up stale or unused data in release management.
Release management admin inheritance
The C3.JarvisAdmin role has the nested roles C3.JarvisUser and C3.ArtifactHubAdmin. Users with the C3.JarvisAdmin role inherit all permissions from the C3.JarvisUser and C3.ArtifactHubAdmin roles.
See Artifact Hub Management Built-in Roles to learn more about the C3.ArtifactHubAdmin role.
Release management user
The typical persona for a user with the C3.JarvisUser role is a developer or engineer who works on code changes. They trigger and monitor builds, manage branches, and focus on code development and testing.
Release management user permissions
The C3.JarvisUser role has the following capabilities to manage one's own builds:
- Abort any running build.
- Access build-related data, such as logs and artifacts.
- Create reports, such as test results and performance metrics.
- Deactivate or reactivate specific branches.
- Manually trigger builds for any branch
- Access read and write configuration keys and secrets for any build.
- Set custom configuration parameters for any build.
- Retrieve performance metrics, such as build duration and test execution time.