Symptom

The absence of a configured connection between a Launch project and a Bitbucket Cloud repository prevents the establishment of automated deployment pipelines, requiring a guided setup of the necessary integration protocols and environment configurations.

Root Cause

Establishing a new project connection involves specific prerequisite steps, including organizational-level app installation and OAuth authorization.

Resolution

To integrate Bitbucket Cloud with Launch, you must complete the following configuration steps:

1. Install the Bitbucket Cloud Marketplace App: Access the Contentstack Marketplace at the organization level to install the Bitbucket Cloud app, which establishes the necessary OAuth permissions for secure communication between the platforms.
2. Connect Bitbucket Cloud to Launch: Create a new project within the Launch dashboard and select Bitbucket as your Git provider; this allows the platform to import your specific repository and branch for the initial deployment.
3. Configure and Deploy: Define the project’s build commands and the output directory (e.g., dist or build) within the environment settings to ensure the platform correctly compiles and serves your source code.
4. Refer to Documentation: Consult the official Contentstack Launch documentation for detailed troubleshooting and advanced environment variable configurations.

Verification

The issue is resolved when the user can successfully create the Launch project and confirm that the repository is connected and building correctly.

Symptom

Connectivity failures within the GIT integration disrupt automated deployment workflows, preventing the synchronization of repository updates with the Launch environment.

Root Cause

Generic integration issues between the platform and the GIT provider resulted in a loss of connectivity, though the specific underlying technical trigger was not identified in the logs.

Resolution

To restore the link between the source repository and Launch, follow these steps:

1. Initiate Reconnection: Access the project's settings and initiate a reconnection with the GIT provider.
2. Repair Connection: Utilize the "Repair Connection" tool to programmatically re-establish the integration and fix connectivity errors.
3. Confirm Status: Verify that the integration is active and that the repository is once again communicating with the platform.

Verification

The issue is resolved when the GIT integration status returns to "Connected" and the user confirms that the case can be closed.

Symptom

The branch selection menu in Launch fails to populate when connecting to a Bitbucket repository. This prevents the selection of source branches, stalling the deployment configuration process.

Root Cause

This issue is typically caused by expired OAuth tokens, insufficient repository permissions, or browser-side session conflicts that block the integration from fetching the repository metadata.

Resolution

1. Re-authenticate the Bitbucket integration within the Launch settings to refresh the connection.
2. Verify that the Bitbucket account has the necessary permissions to access the specific repository and its branches.
3. Ensure the OAuth token used for the integration has been granted the required scopes for repository read access.
4. Use an Incognito browser window or clear the browser cache to rule out session-related display issues.

Verification

Access the project deployment or environment setup screen. The issue is resolved when the "Branch" dropdown menu successfully populates with the list of branches retrieved from the connected Bitbucket repository.