Adobe Cloud Manager comes provisioned with a single git repository that is used to deploy code using Cloud Manager’s CI/CD pipelines. Customers can use the Cloud Manager’s git repository out of the box. Customers also have the option of integrating an on-premise or customer-managed git repository with Cloud Manager.
This video series explores several use cases when it comes to integrating a customer-managed git repository with Cloud Manager, including:
For a complete overview, please review the Cloud Manager User Guide. The video series assumes a basic knowledge of git and source control management. See the additional resources below for more details on git.
The steps and naming conventions outlined in this video series represent some best practices for working with a customer-managed git repository and Cloud Manager. It is expected that the conventions and workflows depicted would be adapted for individual development teams.
First steps for synchronizing a customer-managed Git repository with Cloud Manager’s Git repository.
Set up a basic branching strategy in order to take advantage of Cloud Manager’s production and non-production pipelines.
Use a feature branch to isolate code changes in a customer-managed git repository and synchronize with Cloud Manager’s git repository in order to use a non-production pipeline for code quality and validation testing.
Prepare code for a production release in a customer-managed git repository and synchronize with Cloud Manager’s git repository in order to deploy to stage and production environments.
Synchronize release tags from a Cloud Manager git repository into a customer-managed git repository in order to provide visibility as to what code has been deployed to stage and production environments.