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

Connect your repository

3 minute read
Tutorial— Learning-oriented: a hands-on lesson for when you're new to something.

In this tutorial we will connect a GitHub repository to CloudBees Unify using a sample Go application template, creating the foundation for automated workflows. Along the way we will encounter the GitHub App integration model, repository templates, and how CloudBees Unify connects to source code.

By the end, you will have a working repository connection ready for creating components and workflows.

Prerequisites

Before we begin, ensure you have:

  • A valid GitHub account

  • Access to at least one organization in CloudBees Unify

Create your sample repository

Now we’ll create a new GitHub repository from the CloudBees sample Go app template. This template provides a complete working application that we can use throughout the tutorial series.

  1. Go to the CloudBees sample Go app repository, and select Use this template.

  2. To copy the template repository, select the Create a new repository option.

  3. Do not select Include all branches.

  4. Select your GitHub ID from the options.

  5. Enter a Repository name.

  6. (Optional) Enter a Description.

  7. Select either Public or Private, according to your requirements.

  8. Select Create repository.

Your new repository is created in your GitHub account from the CloudBees sample Go app template. You can see the complete Go application code structure, including source files, tests, and configuration. We are now ready to connect this repository to CloudBees Unify.

Set up the GitHub App integration

Now we’ll connect CloudBees Unify to your new repository by creating a GitHub App integration. This integration allows CloudBees Unify to access your repository and use it in components and workflows.

  1. Select an organization, and then select Configurations  Integrations.

  2. Select Create integration. The list of available integrations displays.

    Create an integration
    Figure 1. Create a new integration

  3. Select GitHub App from the list of available integration types.

  4. Enter a Name for the GitHub App.

  5. (Optional) Enter a Description.

  6. Select Install GitHub App.

This action redirects you to GitHub, where you are prompted to review CloudBees platform permissions.

  1. Select the GitHub account or GitHub organization where you created the sample Go app repository.

  2. Review the permissions and select Save.

GitHub redirects you back to Configurations  Integrations in CloudBees Unify. Your integration is now connected and ready to use.

Verify your repository connection

Let’s confirm that the repository connection is working and available for creating components.

  1. In CloudBees Unify, select Configurations  Integrations.

  2. Locate your new GitHub App integration in the list and confirm it shows a connected status.

If you previously created and authorized a GitHub App, CloudBees Unify reuses the existing app and may skip the permissions review step.

You have confirmed that CloudBees Unify can reach your repository. Notice that GitHub App integrations created for source code access may not appear as standalone entries in Configurations  Integrations, as they are applied automatically when you create components and workflows that reference the repository.

What we accomplished

We have successfully connected a GitHub repository to CloudBees Unify through a secure GitHub App integration. Along the way we encountered repository templates, the GitHub App authorization model, and how CloudBees Unify manages source code connections.

You now have a working repository connection that serves as the foundation for all CloudBees Unify automation features.

From here, you can:

Introduction
Create a build workflow