› Best Practices › Robot Lifecycle Management › Basic setup with Robot Lifecycle Management

Basic setup with Robot Lifecycle Management

Use the following procedure to recreate the basic setup with Robot Lifecycle Management. The procedure gives step-by-step details that demonstrate how to synchronize in and out of a simple bare, file-based Git repository that is commonly referred to as a remote repository.

The Synchronizer supports all types of Git repositories to be the remote repository as long as they adhere to the Git protocol standards to transfer data. Connection to a remote repository through HTTP can only be established if the repository does not require authorization.

You can check the Git online reference material for detailed information on using each type of repository. On the git-scm.com website, search for articles on the protocols, such as "Git on the Server - The Protocols." The Synchronizer supports the following Git protocol standards to transfer data: HTTP(S), SSH, and Git. The main difference is, while a simple bare Git repository resides locally on a file system, the other solutions can be connected to remotely. This choice has an impact on the physical requirements and container compositions.

To perform a basic setup that includes Robot Lifecycle Management, complete the following steps:

  1. Select an applicable branching strategy
  2. Create a bare, file-based Git repository
  3. Configure the Management Consoles
  4. Start the Synchronizers
  5. Promote objects to production and revert changes
  6. Check the synchronization result